public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [RFC v3] tcp: Replace TCP buffer structure by an iovec array
Date: Thu, 21 Mar 2024 23:51:20 +1100	[thread overview]
Message-ID: <ZfwtSHyn1Dq1C_Ei@zatzit> (raw)
In-Reply-To: <ZfwscVAekP-lwnt_@zatzit>

[-- Attachment #1: Type: text/plain, Size: 4259 bytes --]

On Thu, Mar 21, 2024 at 11:47:45PM +1100, David Gibson wrote:
> On Thu, Mar 21, 2024 at 01:21:03PM +0100, Laurent Vivier wrote:
> > On 3/21/24 11:55, David Gibson wrote:
> > > On Thu, Mar 21, 2024 at 09:26:58AM +0100, Laurent Vivier wrote:
> > > > On 3/21/24 02:26, David Gibson wrote:
> > > > > On Wed, Mar 20, 2024 at 05:31:46PM +0100, Laurent Vivier wrote:
> > > > > > To be able to provide pointers to TCP headers and IP headers without
> > > > > > worrying about alignment in the structure, split the structure into
> > > > > > several arrays and point to each part of the frame using an iovec array.
> > > > > > 
> > > > > > Using iovec also allows us to simply ignore the first entry when the
> > > > > > vnet length header is not needed.
> > > > > > 
> > > > > > Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> > > > > 
> > > > > [snip]
> > > > > > +static_assert(MSS4 <= sizeof(tcp4_payload[0].data));
> > > > > 
> > > > > This generates a clang-tidy warning, because apparently the C11
> > > > > version of static_assert() requires a message - making it optional is
> > > > > a C2x extension.
> > > > > 
> > > > > Laurent, I know you're having trouble getting the full testsuite to
> > > > > run (but some ideas on that later today, I hope).  But could you
> > > > > please add a "make cppcheck" and "make clang-tidy" to your pre-post
> > > > > routine.
> > > > > 
> > > > 
> > > > I'll do.
> > > > Thank you to have checked that.
> > > > Are there any other commands to run before to send?
> > > > Something like scripts/chekpatch.pl we have in QEMU?
> > > > 
> > > > I have always the same problem with the test suite, even after a "make
> > > > realclean" in test (see attachment)
> > > > How to debug?
> > > 
> > > Huh.  Guest kernel can't find root.  That's not a fault I was
> > > expecting (and alas, won't be helped by the patch I have in the
> > > works).
> > > 
> > > What's really weird is I don't see any signs of loading the initrd
> > > before that failure, and with the mbuto images we're using we should
> > > never *leave* the initrd.  Which kind of makes sense - if it's not
> > > seeing the initrd, then there is indeed no root to mount.
> > > 
> > > Can you gran the full qemu command line it's trying to use?
> > > 
> > My file mbuto seems to be empty:
> 
> Welp, that would explain it.
> 
> > $ cd test/
> > $ make
> > ./mbuto/mbuto -p ./passt.mem.mbuto -c lz4 -f mbuto.mem.img
> > Applying profile from file ./passt.mem.mbuto
> > depmod: WARNING: could not open modules.builtin.modinfo at
> > /tmp/tmp.0Xr88SNogx/lib/modules/6.7.9-200.fc39.x86_64: No such file or
> > directory
> 
> So now we have two mysteries.  1) Why is depmod failing here, and 2)
> why isn't depmod failing causing mbuto to fail, rather than generating
> nonsense output.

Can you get the output of running mbuto with sh -x?  That might shed
some light.

> 
> > Size: bin  4.9M lib   15M kmod  218k total   20M compressed  4.1k
> > KERNEL=/boot/vmlinuz-6.7.9-200.fc39.x86_64
> > INITRD=/home/lvivier/Projects/passt/test/mbuto.mem.img
> > initramfs mounted at: /tmp/tmp.0Xr88SNogx
> > $ ls -l /home/lvivier/Projects/passt/test/mbuto.mem.img
> > -rw-r--r--. 1 lvivier lvivier 50 Mar 21 13:17 /home/lvivier/Projects/passt/test/mbuto.mem.img
> > $ gzip -d -  < /home/lvivier/Projects/passt/test/mbuto.mem.img|hexdump -C
> > 00000000  30 37 30 37 30 31 30 30  30 30 30 30 30 30 30 30  |0707010000000000|
> > 00000010  30 30 30 30 30 30 30 30  30 30 30 30 30 30 30 30  |0000000000000000|
> > 00000020  30 30 30 30 30 30 30 30  30 30 30 30 30 31 30 30  |0000000000000100|
> > 00000030  30 30 30 30 30 30 30 30  30 30 30 30 30 30 30 30  |0000000000000000|
> > *
> > 00000060  30 30 30 30 30 42 30 30  30 30 30 30 30 30 54 52  |00000B00000000TR|
> > 00000070  41 49 4c 45 52 21 21 21  00 00 00 00 00 00 00 00  |AILER!!!........|
> > 00000080  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> > *
> > 00000200
> > 
> > Thanks,
> > Laurent
> > 
> 



-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-03-21 12:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 16:31 [RFC v3] tcp: Replace TCP buffer structure by an iovec array Laurent Vivier
2024-03-21  0:58 ` David Gibson
2024-03-21  1:26 ` David Gibson
     [not found]   ` <6d0c5777-ed50-4e99-96cb-35aa38d0e129@redhat.com>
2024-03-21 10:55     ` David Gibson
2024-03-21 12:21       ` Laurent Vivier
2024-03-21 12:47         ` David Gibson
2024-03-21 12:51           ` David Gibson [this message]
2024-03-21 14:11             ` Laurent Vivier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZfwtSHyn1Dq1C_Ei@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).