xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wl@xen.org>
To: "Durrant, Paul" <pdurrant@amazon.co.uk>
Cc: "Wei Liu" <liuwe@microsoft.com>, "Wei Liu" <wl@xen.org>,
	"Paul Durrant" <paul@xen.org>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Michael Kelley" <mikelley@microsoft.com>,
	"Xen Development List" <xen-devel@lists.xenproject.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v4 6/7] x86/hyperv: retrieve vp_index from Hyper-V
Date: Tue, 28 Jan 2020 16:53:30 +0000	[thread overview]
Message-ID: <20200128165330.y36ozjw6io7fyucq@debian> (raw)
In-Reply-To: <c6a5c2bc7178499ca4618a76996dc8d4@EX13D32EUC003.ant.amazon.com>

On Tue, Jan 28, 2020 at 04:33:00PM +0000, Durrant, Paul wrote:
> > -----Original Message-----
> > From: Xen-devel <xen-devel-bounces@lists.xenproject.org> On Behalf Of Jan
> > Beulich
> > Sent: 28 January 2020 16:19
> > To: Wei Liu <wl@xen.org>; Paul Durrant <paul@xen.org>; Andrew Cooper
> > <andrew.cooper3@citrix.com>
> > Cc: Xen Development List <xen-devel@lists.xenproject.org>; Roger Pau Monné
> > <roger.pau@citrix.com>; Wei Liu <liuwe@microsoft.com>; Michael Kelley
> > <mikelley@microsoft.com>
> > Subject: Re: [Xen-devel] [PATCH v4 6/7] x86/hyperv: retrieve vp_index from
> > Hyper-V
> > 
> > On 28.01.2020 16:55, Wei Liu wrote:
> > > On Thu, Jan 23, 2020 at 04:48:38PM +0100, Jan Beulich wrote:
> > >> On 22.01.2020 21:23, Wei Liu wrote:
> > >>> This will be useful when invoking hypercall that targets specific
> > >>> vcpu(s).
> > >>>
> > >>> Signed-off-by: Wei Liu <liuwe@microsoft.com>
> > >>> Reviewed-by: Paul Durrant <paul@xen.org>
> > >>
> > >> For formal reasons
> > >> Acked-by: Jan Beulich <jbeulich@suse.com>
> > >>
> > >> However I wonder whether the Viridian entry in MAINTAINERS shouldn't
> > >> be extended by
> > >>
> > >> F:	xen/arch/x86/guest/hyperv/
> > >>
> > >> (and possibly have its title adjusted). Thoughts?
> > >
> > > This isn't about emulating Hyper-V inside Xen, so I don't think that's
> > > the right approach here.
> > 
> > Well, it's the code producing the interface in one case, and
> > consuming it here. So there is some overlap at least.
> > 
> > > That said, if Paul wants to take this under his purview, it's fine by me
> > > -- that would make me easier to upstream my patch. ;-)  I also wouldn't
> > > mind adding myself as maintainer for this path.
> > 
> > Perhaps best both of you? Paul, Andrew, what do you think?
> > 
> 
> IMO it's probably best to the put the Hyper-V stuff under 'Viridian'
> and add yourself as a maintainer there. There really is likely to be
> significant overlap and it'd make it easier (for me at least) to keep
> track of the bigger picture (i.e. Xen using enlightenments as well as
> implementing them).

When you said "yourself", did you mean me or Jan?

Wei.

> 
>   Cheers,
> 
>     Paul

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

  reply	other threads:[~2020-01-28 16:53 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 20:23 [Xen-devel] [PATCH v4 0/7] More Hyper-V infrastructure Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 1/7] x86: provide executable fixmap facility Wei Liu
2020-01-22 20:56   ` Andrew Cooper
2020-01-28 15:09     ` Wei Liu
2020-01-23 11:04   ` Jan Beulich
2020-01-28 15:15     ` Wei Liu
2020-01-28 15:38       ` Jan Beulich
2020-01-29 14:42         ` Wei Liu
2020-01-29 14:59           ` Jan Beulich
2020-01-29 16:37             ` Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page Wei Liu
2020-01-22 21:31   ` Andrew Cooper
2020-01-23 10:04     ` Jan Beulich
2020-01-28 15:19     ` Wei Liu
2020-01-23  1:35   ` Michael Kelley
2020-01-28 15:20     ` Wei Liu
2020-01-23 11:18   ` Jan Beulich
2020-01-23 15:20     ` Michael Kelley
2020-01-28 15:30     ` Wei Liu
2020-01-28 15:41       ` Jan Beulich
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 3/7] x86/hyperv: provide Hyper-V hypercall functions Wei Liu
2020-01-22 21:57   ` Andrew Cooper
2020-01-23 10:13     ` Jan Beulich
2020-01-29 18:25       ` Wei Liu
2020-01-23 11:28   ` Jan Beulich
2020-01-29 18:37     ` Wei Liu
2020-01-30  8:12       ` Jan Beulich
2020-01-30 11:55         ` Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 4/7] DO NOT APPLY: x86/hyperv: issue an hypercall Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 5/7] x86/hyperv: provide percpu hypercall input page Wei Liu
2020-01-23 15:45   ` Jan Beulich
2020-01-28 15:50     ` Wei Liu
2020-01-28 16:15       ` Jan Beulich
2020-01-28 16:52         ` Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 6/7] x86/hyperv: retrieve vp_index from Hyper-V Wei Liu
2020-01-23 15:48   ` Jan Beulich
2020-01-28 15:55     ` Wei Liu
2020-01-28 16:18       ` Jan Beulich
2020-01-28 16:33         ` Durrant, Paul
2020-01-28 16:53           ` Wei Liu [this message]
2020-01-28 17:01             ` Durrant, Paul
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 7/7] x86/hyperv: setup VP assist page Wei Liu
2020-01-22 22:05   ` Andrew Cooper
2020-01-23 15:50   ` Jan Beulich

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=20200128165330.y36ozjw6io7fyucq@debian \
    --to=wl@xen.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=liuwe@microsoft.com \
    --cc=mikelley@microsoft.com \
    --cc=paul@xen.org \
    --cc=pdurrant@amazon.co.uk \
    --cc=roger.pau@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).