xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: Ian Jackson <Ian.Jackson@citrix.com>
Cc: 'Stefano Stabellini' <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>,
	"Tim (Xen.org)" <tim@xen.org>,
	George Dunlap <George.Dunlap@citrix.com>,
	Julien Grall <julien.grall@arm.com>,
	Jan Beulich <jbeulich@suse.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH] tools: specifically enable VirtFS in Linux QEMU builds
Date: Fri, 7 Sep 2018 16:20:09 +0000	[thread overview]
Message-ID: <042555be37d34d4baf26401e8a163db6@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <23442.42208.181389.592660@mariner.uk.xensource.com>

> -----Original Message-----
> From: Ian Jackson [mailto:ian.jackson@citrix.com]
> Sent: 07 September 2018 17:19
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: George Dunlap <George.Dunlap@citrix.com>; Roger Pau Monne
> <roger.pau@citrix.com>; 'Stefano Stabellini' <sstabellini@kernel.org>; Wei
> Liu <wei.liu2@citrix.com>; Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com>; Andrew Cooper
> <Andrew.Cooper3@citrix.com>; Tim (Xen.org) <tim@xen.org>; Julien Grall
> <julien.grall@arm.com>; Jan Beulich <jbeulich@suse.com>; xen-
> devel@lists.xenproject.org
> Subject: RE: [Xen-devel] [PATCH] tools: specifically enable VirtFS in Linux
> QEMU builds
> 
> Paul Durrant writes ("RE: [Xen-devel] [PATCH] tools: specifically enable VirtFS
> in Linux QEMU builds"):
> > George Dunlap [mailto:george.dunlap@citrix.com]
> > > Not the least because the dependencies may change.  I think adding an
> > > "--enable-9pfs" option which will pass on the requisite "--enable" to
> > > qemu (such that qemu build will fail if the prereqs are not present)
> > > makes the most sense.
> >
> > I'd be happy with that if others are.
> 
> SGTM.  I guess there would be osstest patch(es) to add the
> dependencies and pass the new option.

Yes, they would need to follow.

  Paul

> 
> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-09-07 16:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06 12:06 [PATCH] tools: specifically enable VirtFS in Linux QEMU builds Paul Durrant
2018-09-06 12:51 ` George Dunlap
2018-09-06 13:08   ` Paul Durrant
2018-09-06 18:11 ` Stefano Stabellini
2018-09-07  8:35   ` Paul Durrant
2018-09-07 14:57     ` Roger Pau Monné
2018-09-07 15:25       ` George Dunlap
2018-09-07 15:27         ` Paul Durrant
2018-09-07 16:18           ` Ian Jackson
2018-09-07 16:20             ` Paul Durrant [this message]
2018-09-07 16:55           ` Stefano Stabellini
2018-09-07 16:57     ` Stefano Stabellini
2018-09-07 17:00       ` Paul Durrant

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=042555be37d34d4baf26401e8a163db6@AMSPEX02CL03.citrite.net \
    --to=paul.durrant@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.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).