mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: B_B_Singh@DELL.com
Cc: bp@suse.de, stuart.w.hayes@gmail.com, hpa@zytor.com,
	mingo@redhat.com, x86@kernel.org, linux-kernel@vger.kernel.org,
	matt.fleming@intel.com
Subject: RE: [PATCH] x86: Configure NX support earlier in setup_arch
Date: Thu, 13 Nov 2014 13:54:01 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1411131147070.3935@nanos> (raw)
In-Reply-To: <8B2F6FFD0BD1E448853114367400A3730702007068@BLRX7MCDC203.AMER.DELL.COM>

On Thu, 13 Nov 2014, B_B_Singh@DELL.com wrote:
> I feel this can be a valid scenario where user wants to disable the
> memory protection (NX flag disable) for his requirement, in that
> case he will hit this issue.

It's not about feelings. If the user wants to disable NX he can do so
already via the kernel command line.

What that patch is useful for is to prevent an hard to debug boot
crash if the kernel happens to run on some wreckaged BIOS. But it's
not there to support and encourage braindamaged BIOS nonsense.

Thanks,

	tglx





      parent reply	other threads:[~2014-11-13 12:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03  1:47 Stuart Hayes
2014-07-08 22:34 ` Stuart Hayes
2014-07-08 22:38   ` H. Peter Anvin
2014-07-10  0:56     ` Stuart Hayes
2014-07-14 17:22       ` Borislav Petkov
2014-07-14 17:28         ` H. Peter Anvin
2014-07-14 17:35           ` Borislav Petkov
2014-11-13  6:39         ` B_B_Singh
2014-11-13 12:30           ` Borislav Petkov
2014-11-13 13:40             ` B_B_Singh
2014-11-13 15:48             ` Thomas Gleixner
2014-11-13 12:54           ` Thomas Gleixner [this message]

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=alpine.DEB.2.11.1411131147070.3935@nanos \
    --to=tglx@linutronix.de \
    --cc=B_B_Singh@DELL.com \
    --cc=bp@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mingo@redhat.com \
    --cc=stuart.w.hayes@gmail.com \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®