From: Juergen Gross <jgross@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
x86@kernel.org
Cc: hpa@zytor.com, tglx@linutronix.de, mingo@redhat.com
Subject: Re: [PATCH 1/3] x86: provide an init_mem_mapping hypervisor hook
Date: Wed, 26 Jul 2017 09:45:29 +0200 [thread overview]
Message-ID: <52f3b900-cf1c-53db-d954-9010c6d2ff83@suse.com> (raw)
In-Reply-To: <801415f5-5802-e890-eb3c-0ec27ab8412d@oracle.com>
On 25/07/17 16:09, Boris Ostrovsky wrote:
> On 07/25/2017 05:50 AM, Juergen Gross wrote:
>> Provide a hook in hypervisor_x86 called after setting up initial
>> memory mapping.
>>
>> This is needed e.g. by Xen HVM guests to map the hypervisor shared
>> info page.
>
> This is not necessarily a problem specific to guests so I wonder whether
> the hook should be part of x86_platform_ops or some other x86 structure.
I'm fine with any solution. I've chosen the hypervisor struct as right
now there seems to be a need for HVM Xen guests only.
Juergen
next prev parent reply other threads:[~2017-07-26 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 9:50 [PATCH 0/3] fix xen hvm guest with kaslr enabled Juergen Gross
2017-07-25 9:50 ` [PATCH 1/3] x86: provide an init_mem_mapping hypervisor hook Juergen Gross
2017-07-25 14:09 ` Boris Ostrovsky
2017-07-26 7:45 ` Juergen Gross [this message]
2017-07-27 13:07 ` [x86] d5c5dc4bef: PANIC:early_exception kernel test robot
2017-07-25 9:50 ` [PATCH 2/3] xen: split up xen_hvm_init_shared_info() Juergen Gross
2017-07-25 14:19 ` Boris Ostrovsky
2017-07-25 14:48 ` Juergen Gross
2017-07-25 9:50 ` [PATCH 3/3] xen: fix hvm guest with kaslr enabled Juergen Gross
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=52f3b900-cf1c-53db-d954-9010c6d2ff83@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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).