From: Ingo Molnar <mingo@elte.hu>
To: Alex Nixon <alex.nixon@citrix.com>
Cc: Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] change init_gdt to update the gdt via write_gdt, rather than a direct write.
Date: Fri, 15 Aug 2008 18:58:21 +0200 [thread overview]
Message-ID: <20080815165821.GA18777@elte.hu> (raw)
In-Reply-To: <48A5ACFA.7040906@citrix.com>
* Alex Nixon <alex.nixon@citrix.com> wrote:
> From: Alex Nixon <alex.nixon@citrix.com>
> Date: Fri, 15 Aug 2008 11:21:56 +0100
> Subject: [PATCH] change init_gdt to update the gdt via write_gdt, rather than a direct write.
>
> By writing directly, a memory access violation can occur whilst
> hotplugging a CPU if the entry was previously marked read-only.
applied to tip/x86/urgent - thanks Alex.
Ingo
prev parent reply other threads:[~2008-08-15 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 16:21 [PATCH] change init_gdt to update the gdt via write_gdt, rather than a direct write Alex Nixon
2008-08-15 16:58 ` Ingo Molnar [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=20080815165821.GA18777@elte.hu \
--to=mingo@elte.hu \
--cc=Jeremy.Fitzhardinge@citrix.com \
--cc=alex.nixon@citrix.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.