All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: Borislav Petkov <bp@amd64.org>, "mingo@elte.hu" <mingo@elte.hu>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"Herrmann3, Andreas" <Andreas.Herrmann3@amd.com>,
	"Seidel, Conny" <Conny.Seidel@amd.com>,
	"Sarathy, Bhavna" <Bhavna.Sarathy@amd.com>,
	"greg@kroah.com" <greg@kroah.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] x86-32: Fix crashes with CPU hotplug on AMD machines
Date: Thu, 05 Aug 2010 07:14:14 -0700	[thread overview]
Message-ID: <4C5AC736.20903@zytor.com> (raw)
In-Reply-To: <20100805074503.GI18307@amd.com>

On 08/05/2010 12:45 AM, Roedel, Joerg wrote:
> 
> To make sure I understand correctly, you suggest to initialize
> tramponline_pg_dir in the boot sequence of the first cpu and fork
> swapper_pg_dir from it later on?
> 

Correct.

>> I realize this isn't how the 64-bit code works at the moment, but in a
>> lot of ways I think it would be better if it did.
> 
> Yeah, may make sense. This patch already brings the 32 bit
> implementation closer to the 64 bit one. On 64 bit things are somewhat
> simpler because the tramponline page table can be defined at
> compile-time there (contains only 2 pgd_t entries) while on 32 bit we
> have to initialize it at runtime.

Correct, again.  It's unclear to me if we can get away with the very
simple 64-bit approach -- in particular, not including all the 1:1
mappings in the kernel -- for all future users, though.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2010-08-05 14:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04 16:45 [PATCH 0/2] Fix 32-bit CPU hotplug issue on AMD Borislav Petkov
2010-08-04 16:45 ` [PATCH 1/2] x86-32: Fix crashes with CPU hotplug on AMD machines Borislav Petkov
2010-08-04 23:05   ` H. Peter Anvin
2010-08-05  4:48     ` Borislav Petkov
2010-08-05  7:45     ` Roedel, Joerg
2010-08-05 14:14       ` H. Peter Anvin [this message]
2010-08-12 14:41         ` Joerg Roedel
2010-08-12 15:34           ` H. Peter Anvin
2010-08-12 15:47             ` Borislav Petkov
2010-08-12 15:47               ` H. Peter Anvin
2010-08-12 17:38                 ` Borislav Petkov
2010-08-24  7:33                 ` Initial working version (Re: [PATCH 1/2] x86-32: Fix crashes with CPU hotplug on AMD machines) Borislav Petkov
2010-08-29 20:32                   ` [PATCH] x86-32, mm: Add an initial page table for core bootstrapping Borislav Petkov
2010-09-02  9:10                     ` [PATCH -v1.1] " Borislav Petkov
2010-08-12 17:06             ` [PATCH 1/2] x86-32: Fix crashes with CPU hotplug on AMD machines Joerg Roedel
2010-08-12 19:01               ` H. Peter Anvin
2010-08-12 19:04                 ` Joerg Roedel
2010-08-13 12:35                   ` Borislav Petkov
2010-08-16 12:19                     ` Borislav Petkov
2010-08-16 12:38                       ` [PATCH -v2 " Borislav Petkov
2010-08-18 18:41                         ` H. Peter Anvin
2010-08-18 19:09                           ` Borislav Petkov
2010-08-18 20:55                           ` [tip:x86/urgent] x86-32: Fix dummy trampoline-related inline stubs tip-bot for H. Peter Anvin
2010-08-18 20:55                         ` [tip:x86/urgent] x86-32: Separate 1:1 pagetables from swapper_pg_dir tip-bot for Joerg Roedel
2010-08-16 12:39                       ` [PATCH -v2 2/2] x86, cpu hotplug: Fix cpu bringup concurrency issue Borislav Petkov
2010-08-18 19:03                         ` H. Peter Anvin
2010-08-18 19:28                           ` Borislav Petkov
2010-08-18 20:04                             ` H. Peter Anvin
2010-08-19 18:10                               ` [PATCH -v2.1 " Borislav Petkov
2010-08-19 22:58                                 ` [tip:x86/urgent] x86, hotplug: Serialize CPU hotplug to avoid bringup concurrency issues tip-bot for Borislav Petkov
2010-08-04 16:45 ` [PATCH 2/2] x86, cpu hotplug: Fix cpu bringup concurrency issue Borislav Petkov

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=4C5AC736.20903@zytor.com \
    --to=hpa@zytor.com \
    --cc=Andreas.Herrmann3@amd.com \
    --cc=Bhavna.Sarathy@amd.com \
    --cc=Conny.Seidel@amd.com \
    --cc=Joerg.Roedel@amd.com \
    --cc=bp@amd64.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --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 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.