From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, imammedo@redhat.com, maxime.coquelin@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 0/7] Rework vhost memory region updates
Date: Thu, 18 Jan 2018 19:59:35 +0000 [thread overview]
Message-ID: <20180118195934.GD2660@work-vm> (raw)
In-Reply-To: <20180118213321-mutt-send-email-mst@kernel.org>
* Michael S. Tsirkin (mst@redhat.com) wrote:
> On Tue, Jan 16, 2018 at 06:04:01PM +0000, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >
> > Hi,
> > This patch set reworks the way the vhost code handles changes in
> > physical address space layout that came from a discussion with Igor.
> >
> > Its intention is to simplify a lot of the update code,
> > and to make it easier for the postcopy+shared code to
> > do the hugepage alignments that are needed.
> >
> > Instead of inserting/removing each section during the add/del
> > callbacks of the listener, we start afresh and build a list
> > from the add and nop callbacks, then at the end compare the list
> > we've built with the exisiting list.
> >
> > v6
> > Tidy ups from Igor
> > The biggest change is moving the 'Move log_dirty check' to be
> > the last patch in the set.
> >
> > Dr. David Alan Gilbert (7):
> > vhost: Build temporary section list and deref after commit
> > vhost: Simplify ring verification checks
> > vhost: Merge sections added to temporary list
> > vhost: Regenerate region list from changed sections list
> > vhost: Clean out old vhost_set_memory and friends
> > vhost: Merge and delete unused callbacks
> > vhost: Move log_dirty check
> >
> > hw/virtio/trace-events | 6 +
> > hw/virtio/vhost.c | 497 ++++++++++++++++------------------------------
> > include/hw/virtio/vhost.h | 5 +-
> > 3 files changed, 180 insertions(+), 328 deletions(-)
>
>
> Seems to trigger errors with clang runtime sanitizer:
>
> /scm/qemu/hw/virtio/vhost.c:425:26: runtime error: null pointer passed as argument 1, which is declared to never be null
> /usr/include/string.h:64:33: note: nonnull attribute specified here
> /scm/qemu/hw/virtio/vhost.c:425:45: runtime error: null pointer passed as argument 2, which is declared to never be null
> /usr/include/string.h:64:33: note: nonnull attribute specified here
> /scm/qemu/hw/virtio/vhost.c:425:26: runtime error: null pointer passed as argument 1, which is declared to never be null
> /usr/include/string.h:64:33: note: nonnull attribute specified here
> /scm/qemu/hw/virtio/vhost.c:425:45: runtime error: null pointer passed as argument 2, which is declared to never be null
> /usr/include/string.h:64:33: note: nonnull attribute specified here
> /scm/qemu/hw/virtio/vhost.c:425:26: runtime error: null pointer passed as argument 1, which is declared to never be null
> /usr/include/string.h:64:33: note: nonnull attribute specified here
> /scm/qemu/hw/virtio/vhost.c:425:45: runtime error: null pointer passed as argument 2, which is declared to never be null
> /usr/include/string.h:64:33: note: nonnull attribute specified here
> /scm/qemu/hw/virtio/vhost.c:425:26: runtime error: null pointer passed as argument 1, which is declared to never be null
> /usr/include/string.h:64:33: note: nonnull attribute specified here
> /scm/qemu/hw/virtio/vhost.c:425:45: runtime error: null pointer passed as argument 2, which is declared to never be null
> /usr/include/string.h:64:33: note: nonnull attribute specified here
How are you running that test? Can you add this printf and tell me what
it's seeing?
/* Same size, lets check the contents */
fprintf(stderr, "%s: %p %p %d\n", __func__, dev->mem_sections, old_sections, n_old_sections);
changed = memcmp(dev->mem_sections, old_sections,
n_old_sections * sizeof(old_sections[0])) != 0;
I'm seeing a bunch of calls where both pointers are NULL, but
n_old_sections is 0, which feels legal to me.
I guess we could make it:
changed = n_old_sections ? memcmp(....) : false;
just to shut clang up.
Dave
>
>
> > --
> > 2.14.3
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-01-18 19:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 18:04 [Qemu-devel] [PATCH v6 0/7] Rework vhost memory region updates Dr. David Alan Gilbert (git)
2018-01-16 18:04 ` [Qemu-devel] [PATCH v6 1/7] vhost: Build temporary section list and deref after commit Dr. David Alan Gilbert (git)
2018-01-16 18:04 ` [Qemu-devel] [PATCH v6 2/7] vhost: Simplify ring verification checks Dr. David Alan Gilbert (git)
2018-01-16 18:04 ` [Qemu-devel] [PATCH v6 3/7] vhost: Merge sections added to temporary list Dr. David Alan Gilbert (git)
2018-01-16 18:04 ` [Qemu-devel] [PATCH v6 4/7] vhost: Regenerate region list from changed sections list Dr. David Alan Gilbert (git)
2018-01-16 18:04 ` [Qemu-devel] [PATCH v6 5/7] vhost: Clean out old vhost_set_memory and friends Dr. David Alan Gilbert (git)
2018-01-16 18:04 ` [Qemu-devel] [PATCH v6 6/7] vhost: Merge and delete unused callbacks Dr. David Alan Gilbert (git)
2018-01-16 18:04 ` [Qemu-devel] [PATCH v6 7/7] vhost: Move log_dirty check Dr. David Alan Gilbert (git)
2018-01-18 19:33 ` [Qemu-devel] [PATCH v6 0/7] Rework vhost memory region updates Michael S. Tsirkin
2018-01-18 19:59 ` Dr. David Alan Gilbert [this message]
2018-01-18 20:16 ` Michael S. Tsirkin
2018-01-19 10:41 ` Dr. David Alan Gilbert
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=20180118195934.GD2660@work-vm \
--to=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.
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 NNTP newsgroup(s).