From: Andi Kleen <ak@suse.de>
To: Zach Brown <zach.brown@oracle.com>
Cc: linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH 1/2] [x86-64] align per-cpu section to configured cache bytes
Date: Sat, 28 Jan 2006 04:03:10 +0100 [thread overview]
Message-ID: <200601280403.11270.ak@suse.de> (raw)
In-Reply-To: <20060127220242.13917.839.sendpatchset@tetsuo.zabbo.net>
On Friday 27 January 2006 23:02, Zach Brown wrote:
> [x86-64] align per-cpu section to configured cache bytes
>
> Align the start of the per-cpu section to the configured number of bytes in a
> cache line. This stops a BUG_ON() from triggering in load_module() when
> DEFINE_PER_CPU() is used in a module and the section isn't cacheline-aligned.
> Rusty also found this and sent a patch in a while ago
> (http://lkml.org/lkml/2004/10/19/17), I don't know what came of that.
Added.
-Andi
prev parent reply other threads:[~2006-01-28 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 22:02 [PATCH 1/2] [x86-64] align per-cpu section to configured cache bytes Zach Brown
2006-01-27 22:02 ` [PATCH 2/2] [x86] " Zach Brown
2006-01-28 21:26 ` Sam Ravnborg
2006-01-27 23:32 ` [PATCH 1/2] [x86-64] " Sam Ravnborg
2006-01-27 23:45 ` Zach Brown
2006-01-28 3:03 ` Andi Kleen [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=200601280403.11270.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zach.brown@oracle.com \
/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