From: "Michael S. Tsirkin" <mst@redhat.com>
To: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
Cc: pbonzini@redhat.com, snabb-devel@googlegroups.com,
qemu-devel@nongnu.org, tech@virtualopensystems.com
Subject: Re: [Qemu-devel] [PATCH 0/3] vhost-user fixes
Date: Fri, 11 Jul 2014 21:42:04 +0300 [thread overview]
Message-ID: <20140711184204.GB3643@redhat.com> (raw)
In-Reply-To: <20140708140447.7314.87628.stgit@3820>
On Tue, Jul 08, 2014 at 05:05:29PM +0300, Nikolay Nikolaev wrote:
> The latest vhost-user changes changed the VHOST_SET_MEM_TABLE handling.
> Now the memory regions are mapped from dev->mem. The BIOS is registered
> at address 0xfffc0000 which is out of memory boundaries for guests with
> less than 4G RAM. Calling qemu_get_ram_fd with this address causes abort()
> in qemu_get_ram_block with "Bad ram offset".
>
> To prevent this situation we introduce a new function to check if the address
> maps to any RAMBlock - qemu_is_ram_block. This is used in VHOST_SET_MEM_TABLE
> handling to revent the aborting call to qemu_get_ram_fd.
>
> The related vhost-user qtest is also updated to reflect the changes in
> vhost-user message structures.
Ugh this is not good :(. The above change was merged very late,
and now we are seeing fall-out. I guess we'll have to do something like
this, bt mkes one wonder what will this change break, in turn.
Besides, you are not tagging patches either RFC or 2.1, and
you really must. Pls do it next time.
And please find more people to Cc using scripts/get_maintainer.pl.
Paolo, maybe you could look at patch 1?
Thanks!
> ---
>
> Nikolay Nikolaev (3):
> Add qemu_is_ram_block
> vhost-user: Fix VHOST_SET_MEM_TABLE processing
> qtest: Adapt vhost-user-test to latehs vhost-user changes
>
>
> exec.c | 15 +++++++++++++++
> hw/virtio/vhost-user.c | 4 ++++
> include/exec/ram_addr.h | 1 +
> tests/vhost-user-test.c | 11 +++++++++--
> 4 files changed, 29 insertions(+), 2 deletions(-)
>
> --
> Signature
next prev parent reply other threads:[~2014-07-11 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 14:05 [Qemu-devel] [PATCH 0/3] vhost-user fixes Nikolay Nikolaev
2014-07-08 14:05 ` [Qemu-devel] [PATCH 1/3] Add qemu_is_ram_block Nikolay Nikolaev
2014-07-08 14:06 ` [Qemu-devel] [PATCH 2/3] vhost-user: Fix VHOST_SET_MEM_TABLE processing Nikolay Nikolaev
2014-07-11 20:56 ` Paolo Bonzini
2014-07-08 14:06 ` [Qemu-devel] [PATCH 3/3] qtest: Adapt vhost-user-test to latehs vhost-user changes Nikolay Nikolaev
2014-07-11 18:42 ` Michael S. Tsirkin [this message]
2014-07-11 20:57 ` [Qemu-devel] [PATCH 0/3] vhost-user fixes Paolo Bonzini
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=20140711184204.GB3643@redhat.com \
--to=mst@redhat.com \
--cc=n.nikolaev@virtualopensystems.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=snabb-devel@googlegroups.com \
--cc=tech@virtualopensystems.com \
/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).