qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Paul Durrant <Paul.Durrant@citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@citrix.com>,
	"aneesh.kumar@linux.vnet.ibm.com"
	<aneesh.kumar@linux.vnet.ibm.com>,
	Anthony Perard <anthony.perard@citrix.com>,
	Xen-devel <xen-devel@lists.xenproject.org>,
	"gkurz@linux.vnet.ibm.com" <gkurz@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [Xen-devel] RFC: configuring QEMU virtfs for Xen PV(H) guests
Date: Mon, 7 Mar 2016 11:56:15 +0100	[thread overview]
Message-ID: <56DD5E4F.7060906@suse.com> (raw)
In-Reply-To: <20160307105107.GA31271@citrix.com>

On 07/03/16 11:51, Wei Liu wrote:
> On Mon, Mar 07, 2016 at 08:21:46AM +0100, Juergen Gross wrote:
>> Hi Wei,
>>
>> On 15/02/16 14:44, Wei Liu wrote:
>>> On Mon, Feb 15, 2016 at 02:33:05PM +0100, Juergen Gross wrote:
>>>> On 15/02/16 14:16, Wei Liu wrote:
>>>>> On Mon, Feb 15, 2016 at 09:07:13AM +0000, Paul Durrant wrote:
>>>>>>>
>>>>> [...]
>>>>>>> # Option 2: Invent a xen-9p device
>>>>>>>
>>>>>>> Another way of doing it is to expose a dummy xen-9p device, so that we
>>>>>>> can use -fsdev XXX -device xen-9p,YYY.  This simple device should be
>>>>>>> used to capture the parameters like mount_tag and fsdev_id, and then
>>>>>>> chained itself to a known location.  Later Xen transport can traverse
>>>>>>> this known location. This xen-9p device doesn't seem to fit well into
>>>>>>> the hierarchy. The best I can think of its parent should be
>>>>>>> TYPE_DEVICE.  In this case:
>>>>>>>
>>>>>>> 1. Toolstack arranges some xenstore entries.
>>>>>>> 2. Toolstack arranges command line options for QEMU:
>>>>>>>       -fsdev XXX -device xen-9p,XXX
>>>>>>> 3. QEMU starts up in xen-attach mode, scans xenstore for relevant
>>>>>>>    entries, then traverses the known location.
>>>>>>>
>>>>>>> Downside: Inventing a dummy device looks suboptimal to me.
>>>>
>>>> Sorry, didn't notice this thread before.
>>>>
>>>
>>> No need to be sorry. I posted this last Friday night. I wouldn't expect
>>> many replies on Monady.
>>>
>>>> For Xen pvUSB backend in qemu I need a Xen system device acting as
>>>> parent for being able to attach/detach virtual USB busses.
>>>>
>>>> I haven't had time to update my patches for some time, but the patch
>>>> for this system device is rather easy. It could be used as a parent
>>>> of the xen-9p devices, too.
>>>>
>>>> I've attached the patch for reference.
>>>>
>>>
>>> Thanks. I will have a look at your patch.
>>
>> Did you have some time to look at the patch? I'm asking because I
>> finally found some time to start working on V2 of my qemu based pvUSB
>> backend. Stefano asked me to hide the system device in my backend and
>> I want to avoid that in case you are needing it, too.
>>
> 
> Yes. I need this device. I'm not sure what "hiding this device in
> backend" means though.

Stefano wanted it to be pvusb backend private: instead of adding it to
hw/xenpv/xen_machine_pv.c he wanted me to add it to hw/usb/xen-usb.c
where it would be usable by the pvUSB backend only.

With you needing that device I can leave the patch more or less
unmodified (some rebasing to the actual qemu version is needed).

Thanks for looking into the patch,

Juergen

  reply	other threads:[~2016-03-07 10:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 19:10 [Qemu-devel] RFC: configuring QEMU virtfs for Xen PV(H) guests Wei Liu
2016-02-15  9:07 ` Paul Durrant
2016-02-15 13:16   ` Wei Liu
2016-02-15 13:23     ` Paul Durrant
2016-02-15 13:33     ` [Qemu-devel] [Xen-devel] " Juergen Gross
2016-02-15 13:44       ` Wei Liu
2016-03-07  7:21         ` Juergen Gross
2016-03-07 10:51           ` Wei Liu
2016-03-07 10:56             ` Juergen Gross [this message]
2016-03-07 10:59               ` Wei Liu
2016-02-15 17:07 ` [Qemu-devel] " Stefano Stabellini

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=56DD5E4F.7060906@suse.com \
    --to=jgross@suse.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=Stefano.Stabellini@citrix.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=anthony.perard@citrix.com \
    --cc=gkurz@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).