From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH] MAINTAINERS: move hvmloader to x86
Date: Tue, 4 Nov 2014 10:47:10 +0000 [thread overview]
Message-ID: <5458AEAE.9080804@citrix.com> (raw)
In-Reply-To: <5458BBF30200007800044B69@mail.emea.novell.com>
On 04/11/14 10:43, Jan Beulich wrote:
> ... as being more like a hypervisor extension into the guest than a
> part of the tool stack.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
I think this is a very sensible idea, but...
>
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -344,6 +344,7 @@ S: Supported
> L: xen-devel@lists.xen.org
> F: xen/arch/x86/
> F: xen/include/asm-x86/
> +F: tools/firmware/hvmloader/
hvmloader as a binary is linked together with other bits in
tools/firmware, which form part of the x86 HVM boot path.
As a result, I would recommend this path being "tools/firmware/" to
include these other bits in being part of the x86 architecture code.
~Andrew
>
> X86 MEMORY MANAGEMENT
> M: Tim Deegan <tim@xen.org>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-11-04 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 10:43 [PATCH] MAINTAINERS: move hvmloader to x86 Jan Beulich
2014-11-04 10:44 ` Ian Campbell
2014-11-04 10:47 ` Andrew Cooper [this message]
2014-11-04 11:20 ` Jan Beulich
2014-11-04 11:29 ` Ian Campbell
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=5458AEAE.9080804@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.