From: Thiemo Seufer <ths@networkno.de>
To: Filip Navara <xnavara@volny.cz>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Intel cache info
Date: Sun, 9 Sep 2007 16:04:15 +0100 [thread overview]
Message-ID: <20070909150415.GA10713@networkno.de> (raw)
In-Reply-To: <5b31733c0709081227w3e5f1036odbc649edfdc8c79b@mail.gmail.com>
Filip Navara wrote:
> Fix the CPUID function 2 to correctly report cache info for the particular
> processor. I chose the values closest to the ones reported in the AMD
> registers. This is important for operating systems that detect cache line
> width and later call CLFLUSH for each line. In the previous implementation
> the values didn't specify L2 cache line width and so Darwin endlessly looped
> trying to flush them.
No patch attached.
Thiemo
next prev parent reply other threads:[~2007-09-09 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 19:27 [Qemu-devel] [PATCH] Intel cache info Filip Navara
2007-09-09 13:47 ` Dan Kenigsberg
2007-09-09 15:04 ` Thiemo Seufer [this message]
2007-09-11 7:20 ` Filip Navara
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=20070909150415.GA10713@networkno.de \
--to=ths@networkno.de \
--cc=qemu-devel@nongnu.org \
--cc=xnavara@volny.cz \
/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;
as well as URLs for NNTP newsgroup(s).