From: Julien Grall <julien.grall@linaro.org>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
josh@joshtriplett.org, sam@ravnborg.org,
Michal Marek <mmarek@suse.cz>,
Randy Dunlap <rdunlap@infradead.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
kvm@vger.kernel.org, x86@kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
mtosatti@redhat.com, Pekka Enberg <penberg@kernel.org>,
Fengguang Wu <fengguang.wu@intel.com>,
Sasha Levin <levinsasha928@gmail.com>,
David Rientjes <rientjes@google.com>,
xen-devel@lists.xenproject.org, Borislav Petkov <bp@suse.de>,
David Vrabel <david.vrabel@citrix.com>,
Benjamin Poirier <bpoirier@suse.de>
Subject: Re: [Xen-devel] [PATCH v3 2/2] x86, arm64, platform, xen, kconfig: add xen defconfig helper
Date: Tue, 09 Dec 2014 20:37:45 +0000 [thread overview]
Message-ID: <54875D99.6070301@linaro.org> (raw)
In-Reply-To: <CAB=NE6V+kLaZePAzHim0VxGsd8ew6dS7kN=H=awwz1dpHy5VJw@mail.gmail.com>
On 09/12/14 20:22, Luis R. Rodriguez wrote:
> On Tue, Dec 9, 2014 at 1:06 AM, Julien Grall <julien.grall@linaro.org> wrote:
>> Hello Luis,
>>
>> On 08/12/2014 23:05, Luis R. Rodriguez wrote:
>>>
>>> diff --git a/kernel/configs/xen.config b/kernel/configs/xen.config
>>> new file mode 100644
>>> index 0000000..0d0eb6d
>>> --- /dev/null
>>> +++ b/kernel/configs/xen.config
>>> +CONFIG_XEN_MCE_LOG=y
>>
>>
>> MCE is x86 specific.
>
> That's what I thought too but its available for arm64, so should we
> fix that Kconfig to depend on x86?
Are you sure? On the Linus's repo I have:
config XEN_MCE_LOG
bool "Xen platform mcelog"
depends on XEN_DOM0 && X86_64 && X86_MCE
Anyway, the MCE interface in the hypervisor is implemented in arch/x86
not in common code.
>>> +CONFIG_XEN_HAVE_PVMMU=y
>>
>>
>> We don't have PVMMU support on ARM. Shouldn't you move this config in
>> architecture specific code?
>
> If you are sure then yes.
I'm 100% sure. MMU is handled by the hardware on ARM.
Thinking a bit more about this option. CONFIG_XEN_HAVE_PVMMU can't be
selected by the user. It's automatically added per platform (for
instance see arch/x86/xen/Kconfig).
So maybe it should not even appear in the one of the fragment configs?
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-12-09 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 23:04 [PATCH v3 0/2]: x86/arm64: add xenconfig Luis R. Rodriguez
2014-12-08 23:04 ` [PATCH v3 1/2] x86, platform, kconfig: clarify kvmconfig is for kvm Luis R. Rodriguez
2014-12-09 17:28 ` Borislav Petkov
2014-12-08 23:05 ` [PATCH v3 2/2] x86, arm64, platform, xen, kconfig: add xen defconfig helper Luis R. Rodriguez
2014-12-09 9:06 ` [Xen-devel] " Julien Grall
2014-12-09 20:22 ` Luis R. Rodriguez
2014-12-09 20:22 ` Luis R. Rodriguez
2014-12-09 20:37 ` Julien Grall [this message]
2014-12-09 23:27 ` Luis R. Rodriguez
2014-12-08 23:53 ` [PATCH v3 0/2]: x86/arm64: add xenconfig Josh Triplett
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=54875D99.6070301@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=bp@suse.de \
--cc=bpoirier@suse.de \
--cc=david.vrabel@citrix.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=josh@joshtriplett.org \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mmarek@suse.cz \
--cc=mtosatti@redhat.com \
--cc=penberg@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=sam@ravnborg.org \
--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).