All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "Berck E. Nash" <flyboy@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: x2apic boot failure on recent sandy bridge system
Date: Mon, 12 Dec 2011 15:42:16 -0800	[thread overview]
Message-ID: <4EE69158.5080805@zytor.com> (raw)
In-Reply-To: <CAE9FiQXf2GzR2Uuw23CK7YVN4djtCd+aOFTRrf=96u9NTXRn=A@mail.gmail.com>

On 12/11/2011 07:40 PM, Yinghai Lu wrote:
> -v2: use x2apic_disabled instead of nox2apic, Suggested by Thomas
>      update x2apic_supported with x2apic_disabled, Suggested by Thomas

This is ugly.  Typically we have no- for boolean options.  If we have a
multivalue option it should be option=value, i.e. x2apic=disabled.  We
can allow x2apic_supported as a backwards compatibility option.

	-hpa


  parent reply	other threads:[~2011-12-12 23:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10  1:56 x2apic boot failure on recent sandy bridge system Berck E. Nash
2011-12-10 20:17 ` Yinghai Lu
2011-12-10 22:58   ` Berck E. Nash
2011-12-10 23:11     ` Yinghai Lu
2011-12-11  7:57   ` Ingo Molnar
2011-12-11 21:43     ` Yinghai Lu
2011-12-11 22:05       ` Berck E. Nash
2011-12-12  3:40         ` Yinghai Lu
2011-12-12 23:21           ` Berck E. Nash
2011-12-13  0:25             ` Suresh Siddha
2011-12-13  1:29               ` Yinghai Lu
2011-12-13  1:41                 ` Suresh Siddha
2011-12-13  4:32                   ` Yinghai Lu
2011-12-13  5:13                     ` Yinghai Lu
2011-12-16 13:59                       ` Berck E. Nash
2011-12-18  8:47                         ` Ingo Molnar
2011-12-12 23:42           ` H. Peter Anvin [this message]
2011-12-13  1:25             ` Yinghai Lu
2011-12-12  7:23       ` Suresh Siddha
     [not found] <fa.1zfuXwqYK6u81uBoo3IdpawcpWw@ifi.uio.no>
     [not found] ` <fa.p3cpkKIGUNv0/iot3o7KT9bb98M@ifi.uio.no>
     [not found]   ` <fa.iPHW7usT23k+cCA19L3eXEDu91Q@ifi.uio.no>
     [not found]     ` <fa.7eOK+XcsKUWU4ZXhBj2K6znxrvc@ifi.uio.no>
     [not found]       ` <fa.VGxfKOh1Z07X1TXm5PxMIlV4xu8@ifi.uio.no>
     [not found]         ` <fa.eH+BpYDdp4xIWE4V+wJu6hFrVxM@ifi.uio.no>
2012-10-19 20:42           ` rrl125
2012-10-19 23:03             ` Suresh Siddha
2012-10-19 23:32               ` Yinghai Lu
2012-10-19 23:36                 ` H. Peter Anvin
2012-10-20  0:02                   ` Suresh Siddha
2012-10-20  0:41                     ` Yinghai Lu
  -- strict thread matches above, loose matches on Subject: below --
2011-12-10  1:46 Berck E. Nash

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=4EE69158.5080805@zytor.com \
    --to=hpa@zytor.com \
    --cc=flyboy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=yinghai@kernel.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.