All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: David Vrabel <david.vrabel@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Alok Kataria <akataria@vmware.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC Linux] x86/xen: allow using x2APIC under Xen without CONFIG_XEN enabled
Date: Mon, 31 Aug 2015 15:19:51 -0400	[thread overview]
Message-ID: <55E4A8D7.4030308@oracle.com> (raw)
In-Reply-To: <55D5DE76020000780009C2B5@prv-mh.provo.novell.com>

On 08/20/2015 08:04 AM, Jan Beulich wrote:
> While commit 4cca6ea04d31c claims to not have any functional effect on
> Xen, this isn't the case: Before that change, kernels built without
> CONFIG_XEN_PVHVM (a dependency which meanwhile became just CONFIG_XEN)
> were able to run in x2APIC mode just fine. Restore that behavior.
>
> This, however, still doesn't fix the case where CONFIG_HYPERVISOR_GUEST
> is not enabled, but I suppose this may be regarded as intentional.
>
> Signed-off-by: Jan Beulich<jbeulich@suse.com>
> ---
> The patch is RFC solely because the way the issue gets fixed doesn't
> look very neat, but I couldn't figure out a better way.

(+ x86 maintainers)

Can we provide something like xen_stub.c (that will have its own 
x86_hyper ops, probably only x2apic_available and maybe detect) which is 
built when !CONFIG_XEN?

Otherwise I see little reason to keep x2apic_available op and we should 
revert the portion of 4cca6ea04d31c that introduced it.

-boris

> ---
>   arch/x86/kernel/cpu/hypervisor.c |    4 ++++
>   1 file changed, 4 insertions(+)
>
> --- 4.2-rc7/arch/x86/kernel/cpu/hypervisor.c
> +++ 4.2-rc7-x86-xen-x2apic-available/arch/x86/kernel/cpu/hypervisor.c
> @@ -81,6 +81,10 @@ void __init init_hypervisor_platform(voi
>   
>   bool __init hypervisor_x2apic_available(void)
>   {
> +#ifndef CONFIG_XEN
> +	if (xen_x2apic_para_available())
> +		return true;
> +#endif
>   	return x86_hyper                   &&
>   	       x86_hyper->x2apic_available &&
>   	       x86_hyper->x2apic_available();
>
>
>


  parent reply	other threads:[~2015-08-31 19:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 12:04 [PATCH RFC Linux] x86/xen: allow using x2APIC under Xen without CONFIG_XEN enabled Jan Beulich
2015-08-31 19:19 ` Boris Ostrovsky
2015-08-31 19:19 ` Boris Ostrovsky [this message]
2015-09-01  6:45   ` Jan Beulich
2015-09-01  6:45   ` 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=55E4A8D7.4030308@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=akataria@vmware.com \
    --cc=david.vrabel@citrix.com \
    --cc=hpa@zytor.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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.