All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
	"Damjan Marion (damarion)" <damarion@cisco.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] vhost-user: broken mem regions
Date: Wed, 25 Jun 2014 20:00:59 +0200	[thread overview]
Message-ID: <53AB0E5B.5060000@redhat.com> (raw)
In-Reply-To: <CADDJ2=Oc0Xk54nsWK8GhkdT9mLL+YON8B9tY25KgdD2u0UrsWw@mail.gmail.com>

Il 25/06/2014 19:06, Nikolay Nikolaev ha scritto:
>> > I understand now what you mean.  Yeah, the format should be changed
>> > to include the offset (why does vhost-user need the ua at all?
>> > perhaps the offset can replace the ua).
> I am trying to do the math here. So if this file is mapped by QEMU
> into a single file then probably
> (region[4].ua - region[3].ua) should give you the offset. And also
> (region[4].ua - region[1].ua) shoudl give the above 3G offset. Or I am
> missing something?

This is correct, but in principle it's not required to map all the 
areas.  The lowest region could correspond to a offset=65536, or 
something like that.  It's better to change the vring values to use 
offsets instead of absolute addresses.

Paolo

  reply	other threads:[~2014-06-25 18:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A459CE38-2929-47A2-8683-8D7EAF0325C0@cisco.com>
     [not found] ` <20140625135207.GC14578@redhat.com>
2014-06-25 14:06   ` [Qemu-devel] vhost-user: broken mem regions Damjan Marion (damarion)
2014-06-25 14:13     ` Nikolay Nikolaev
2014-06-25 14:16       ` Michael S. Tsirkin
2014-06-25 14:20       ` Damjan Marion (damarion)
2014-06-25 14:27         ` Michael S. Tsirkin
2014-06-25 14:57           ` Damjan Marion (damarion)
2014-06-25 15:29             ` Michael S. Tsirkin
2014-06-25 15:46               ` Damjan Marion (damarion)
2014-06-25 15:50                 ` Michael S. Tsirkin
2014-06-25 16:30                   ` Damjan Marion (damarion)
2014-06-25 16:44                     ` Paolo Bonzini
2014-06-25 16:56                       ` Nikolay Nikolaev
2014-06-25 17:05                         ` Paolo Bonzini
2014-06-25 18:11                           ` Michael S. Tsirkin
2014-06-25 18:07                         ` Michael S. Tsirkin
2014-06-25 18:13                           ` Nikolay Nikolaev
2014-06-25 18:18                             ` Michael S. Tsirkin
2014-06-25 21:37                               ` Damjan Marion (damarion)
2014-06-26 10:03                                 ` Nikolay Nikolaev
2014-06-25 17:06                       ` Nikolay Nikolaev
2014-06-25 18:00                         ` Paolo Bonzini [this message]
2014-06-25 21:52                       ` Damjan Marion (damarion)
2014-06-26  7:13                         ` Michael S. Tsirkin
2014-06-26  7:44                           ` Damjan Marion (damarion)
2014-06-26  7:56                             ` Michael S. Tsirkin
2014-06-26  8:26                               ` Damjan Marion (damarion)
     [not found] ` <CADDJ2=M3=mxjHO3=gNq5xKseDyrJkaBVFLkb=SsFr0_d9UUBsQ@mail.gmail.com>
2014-06-25 14:16   ` Damjan Marion (damarion)

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=53AB0E5B.5060000@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=damarion@cisco.com \
    --cc=mst@redhat.com \
    --cc=n.nikolaev@virtualopensystems.com \
    --cc=qemu-devel@nongnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.