From: "H. Peter Anvin" <hpa@zytor.com>
To: Hans Rosenfeld <hans.rosenfeld@amd.com>
Cc: "mingo@redhat.com" <mingo@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:x86/cpu] x86, cpu: AMD errata checking framework
Date: Thu, 08 Jul 2010 08:08:55 -0700 [thread overview]
Message-ID: <4C35EA07.9020409@zytor.com> (raw)
In-Reply-To: <20100708141845.GI11824@escobedo.osrc.amd.com>
On 07/08/2010 07:18 AM, Hans Rosenfeld wrote:
>
> Thats exactly the kind of thing I wanted to avoid. This means carrying
> around all errata definitions in memory all the time instead of just
> when theres actually code thats using them.
>
On a note on that... by passing the definition as arguments you're doing
it asas *code*, which is seriously bloated over a memory structure. The
size of memory structures should be insignificant, and would be cold in
memory anyway.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-07-08 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1276681733-10872-1-git-send-email-hans.rosenfeld@amd.com>
2010-06-17 17:06 ` [tip:x86/cpu] x86, cpu: AMD errata checking framework tip-bot for Hans Rosenfeld
2010-07-07 17:13 ` H. Peter Anvin
2010-07-08 14:18 ` Hans Rosenfeld
2010-07-08 14:59 ` H. Peter Anvin
2010-07-08 18:00 ` Hans Rosenfeld
2010-07-08 15:02 ` H. Peter Anvin
2010-07-08 15:08 ` H. Peter Anvin [this message]
[not found] <1280336972-865982-1-git-send-email-hans.rosenfeld@amd.com>
2010-07-28 23:27 ` tip-bot for Hans Rosenfeld
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=4C35EA07.9020409@zytor.com \
--to=hpa@zytor.com \
--cc=hans.rosenfeld@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--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.