From: Jan Beulich <jbeulich@suse.com>
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
Date: Tue, 28 Jan 2020 17:18:33 +0100 [thread overview]
Message-ID: <568d6410-ad85-74f8-84ab-2c5e47d2c314@suse.com> (raw)
In-Reply-To: <20200128155510.ruie6ck4i3hg5dub@debian>
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?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-01-28 16:18 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 [this message]
2020-01-28 16:33 ` Durrant, Paul
2020-01-28 16:53 ` Wei Liu
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=568d6410-ad85-74f8-84ab-2c5e47d2c314@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=liuwe@microsoft.com \
--cc=mikelley@microsoft.com \
--cc=paul@xen.org \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--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).