From: Greg Kurz <groug@kaod.org>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: mszeredi@redhat.com, "Daniel P. Berrangé " <berrange@redhat.com>,
qemu-devel@nongnu.org, stefanha@redhat.com,
marcandre.lureau@redhat.com,
"Paolo Bonzini" <pbonzini@redhat.com>,
vgoyal@redhat.com
Subject: Re: virtiofsd: Where should it live?
Date: Tue, 3 Dec 2019 17:08:44 +0100 [thread overview]
Message-ID: <20191203170844.1defe3f0@bahia.w3ibm.bluemix.net> (raw)
In-Reply-To: <20191203131046.GF3078@work-vm>
On Tue, 3 Dec 2019 13:10:46 +0000
"Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:
> * Paolo Bonzini (pbonzini@redhat.com) wrote:
> > On 03/12/19 14:02, Dr. David Alan Gilbert wrote:
> > >> It could be in fsdev/virtiofsd,
> > > fsdev is currently all 9p stuff, so that would seem very confusing.
> >
> > Move it to fsdev/9p?
>
> Greg: Are you OK with us doing that, and then having fsdev/virtiofsd for
> our side of things?
>
That's okay with me.
> > >> but I agree with Daniel that at this
> > >> point the QEMU build system introduces baggage that you may not want for
> > >> virtiofsd.
> > >
> > > I've already got it wired up in contrib with qemu's build system
> > > so that doesn't seem to be an issue. The question is purely a 'where'.
> >
> > Oh I agree it's not an insurmountable problem. For a new project I may
> > not want to deal with the complicated rules.mak stuff; however, if
> > virtiofsd doesn't have to do anything complicated then it's your choice.
>
> Fortunately we don't seem to have touched that.
>
> Dave
>
> > Paolo
> >
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
next prev parent reply other threads:[~2019-12-03 16:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 18:50 virtiofsd: Where should it live? Dr. David Alan Gilbert
2019-11-26 9:02 ` Marc-André Lureau
2019-11-26 11:42 ` Dr. David Alan Gilbert
2019-11-26 10:26 ` Daniel P. Berrangé
2019-11-26 12:14 ` Dr. David Alan Gilbert
2019-12-02 10:12 ` Peter Maydell
2019-12-02 12:56 ` Markus Armbruster
2019-12-02 13:32 ` Thomas Huth
2019-12-02 15:39 ` Markus Armbruster
2019-12-02 15:55 ` Dr. David Alan Gilbert
2019-12-03 10:53 ` Dr. David Alan Gilbert
2019-12-03 11:06 ` Peter Maydell
2019-12-03 11:17 ` Dr. David Alan Gilbert
2019-12-03 11:19 ` Daniel P. Berrangé
2019-12-03 13:06 ` Dr. David Alan Gilbert
2019-12-04 7:43 ` Markus Armbruster
2019-12-04 8:17 ` Gerd Hoffmann
2019-12-04 13:28 ` Kevin Wolf
2019-12-04 13:29 ` Thomas Huth
2019-12-04 14:36 ` Eric Blake
2019-12-04 16:33 ` Dr. David Alan Gilbert
2019-12-04 12:04 ` Dr. David Alan Gilbert
2019-12-04 13:10 ` Markus Armbruster
2019-12-04 14:34 ` Eric Blake
2019-12-03 12:59 ` Paolo Bonzini
2019-12-03 13:02 ` Dr. David Alan Gilbert
2019-12-03 13:07 ` Paolo Bonzini
2019-12-03 13:10 ` Dr. David Alan Gilbert
2019-12-03 16:08 ` Greg Kurz [this message]
2019-12-02 9:37 ` Michael S. Tsirkin
2019-12-02 16:44 ` Dr. David Alan Gilbert
2019-12-02 16:52 ` Michael S. Tsirkin
2019-12-02 17:01 ` Dr. David Alan Gilbert
2019-12-02 17:16 ` Christophe de Dinechin
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=20191203170844.1defe3f0@bahia.w3ibm.bluemix.net \
--to=groug@kaod.org \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mszeredi@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.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).