All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	stratos-dev@op-lists.linaro.org,
	Oleksandr Tyshchenko <olekstysh@gmail.com>,
	xen-devel@lists.xen.org,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Juergen Gross <jgross@suse.com>,
	Sebastien Boeuf <sebastien.boeuf@intel.com>,
	Liu Jiang <gerry@linux.alibaba.com>,
	Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: [virtio-dev] Re: [PATCH V3 0/2] qemu: vhost-user: Support Xen memory mapping quirks
Date: Wed, 05 Apr 2023 11:00:34 +0100	[thread overview]
Message-ID: <87h6tulkae.fsf@linaro.org> (raw)
In-Reply-To: <20230405080512.nvxiw4lv7hyuzqej@vireshk-i7>


Viresh Kumar <viresh.kumar@linaro.org> writes:

> On 09-03-23, 14:20, Viresh Kumar wrote:
>> Hello,
>> 
>> This patchset tries to update the vhost-user protocol to make it support special
>> memory mapping required in case of Xen hypervisor.
>> 
>> The first patch is mostly cleanup and second one introduces a new xen specific
>> feature.
>
> Can we apply this now ? I have developed code for rust-vmm crates
> based on this and we need to get this merged/finalized first before
> merging those changes.


I've queued into my virtio/vhost-user-device series so I'll get merged
with that series unless mst wants to take it now.

>
> Thanks.


-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


WARNING: multiple messages have this Message-ID (diff)
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	stratos-dev@op-lists.linaro.org,
	Oleksandr Tyshchenko <olekstysh@gmail.com>,
	xen-devel@lists.xen.org,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Juergen Gross <jgross@suse.com>,
	Sebastien Boeuf <sebastien.boeuf@intel.com>,
	Liu Jiang <gerry@linux.alibaba.com>,
	Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: Re: [PATCH V3 0/2] qemu: vhost-user: Support Xen memory mapping quirks
Date: Wed, 05 Apr 2023 11:00:34 +0100	[thread overview]
Message-ID: <87h6tulkae.fsf@linaro.org> (raw)
In-Reply-To: <20230405080512.nvxiw4lv7hyuzqej@vireshk-i7>


Viresh Kumar <viresh.kumar@linaro.org> writes:

> On 09-03-23, 14:20, Viresh Kumar wrote:
>> Hello,
>> 
>> This patchset tries to update the vhost-user protocol to make it support special
>> memory mapping required in case of Xen hypervisor.
>> 
>> The first patch is mostly cleanup and second one introduces a new xen specific
>> feature.
>
> Can we apply this now ? I have developed code for rust-vmm crates
> based on this and we need to get this merged/finalized first before
> merging those changes.


I've queued into my virtio/vhost-user-device series so I'll get merged
with that series unless mst wants to take it now.

>
> Thanks.


-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2023-04-05 10:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09  8:50 [virtio-dev] [PATCH V3 0/2] qemu: vhost-user: Support Xen memory mapping quirks Viresh Kumar
2023-03-09  8:50 ` Viresh Kumar
2023-03-09  8:51 ` [virtio-dev] [PATCH V3 1/2] docs: vhost-user: Define memory region separately Viresh Kumar
2023-03-09  8:51   ` Viresh Kumar
2023-03-15 15:19   ` [virtio-dev] " Stefan Hajnoczi
2023-03-15 15:19     ` Stefan Hajnoczi
2023-03-28 11:27   ` [virtio-dev] " Alex Bennée
2023-03-28 11:27     ` Alex Bennée
2023-03-09  8:51 ` [virtio-dev] [PATCH V3 2/2] docs: vhost-user: Add Xen specific memory mapping support Viresh Kumar
2023-03-09  8:51   ` Viresh Kumar
2023-03-15 15:23   ` [virtio-dev] " Stefan Hajnoczi
2023-03-15 15:23     ` Stefan Hajnoczi
2023-03-28 11:28   ` [virtio-dev] " Alex Bennée
2023-03-28 11:28     ` Alex Bennée
2023-03-15  5:17 ` [virtio-dev] Re: [PATCH V3 0/2] qemu: vhost-user: Support Xen memory mapping quirks Viresh Kumar
2023-03-15  5:17   ` Viresh Kumar
2023-03-15 15:25 ` [virtio-dev] " Stefan Hajnoczi
2023-03-15 15:25   ` Stefan Hajnoczi
2023-04-05  8:05 ` [virtio-dev] " Viresh Kumar
2023-04-05  8:05   ` Viresh Kumar
2023-04-05 10:00   ` Alex Bennée [this message]
2023-04-05 10:00     ` Alex Bennée
2023-04-05 10:06     ` [virtio-dev] " Michael S. Tsirkin
2023-04-05 10:06       ` Michael S. Tsirkin
2023-04-05 10:24       ` [virtio-dev] " Alex Bennée
2023-04-05 10:24         ` Alex Bennée
2023-04-05 10:44         ` [virtio-dev] " Michael S. Tsirkin
2023-04-05 10:44           ` Michael S. Tsirkin

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=87h6tulkae.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=gerry@linux.alibaba.com \
    --cc=jgross@suse.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=mst@redhat.com \
    --cc=olekstysh@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sebastien.boeuf@intel.com \
    --cc=stefanha@redhat.com \
    --cc=stratos-dev@op-lists.linaro.org \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=xen-devel@lists.xen.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 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.