From: Takanori Kawano <t-kawano@ebina.hitachi.co.jp>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Question about wbinvd
Date: Wed, 05 Jun 2002 05:33:52 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905639@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905635@msgid-missing>
I expect ACPI_FLUSH_CPU_CACHE to use SAL_CACHE_FLUSH because
there are already some ia64 boxes that have platform(non-processor)
caches.
Thanks,
---
Takanori Kawano
Hitachi Ltd,
Internet Systems Platform Division
t-kawano@ebina.hitachi.co.jp
>>>>>> On Tue, 4 Jun 2002 10:13:43 -0700, "Grover, Andrew" <andrew.grover@intel.com> said:
>
> Andy> I don't know if it is not necessary or not. We changed it
> Andy> because "wbinvd" is a IA32-ism. IA64 may need to define
> Andy> ACPI_FLUSH_CPU_CACHE to something appropriate.
>
>The current implementation is most likely broken. I'm not exactly
>sure what the requirements of ACPI_FLUSH_CPU_CACHE are, that's why I'm
>saying "most likely". I suspect it ought to be using the SAL rather
>than the PAL flush cache routines (so that off-chip caches get
>flushed, too). Also, IIRC, the latest interpretation of the SAL
>cache-flush routines is that they flush the caches only on the CPU
>that is making the call. So, if the intent is to flush all the caches
>on all CPUs, an IPI would be needed.
>
> --david
>
>_______________________________________________
>Linux-IA64 mailing list
>Linux-IA64@linuxia64.org
>http://lists.linuxia64.org/lists/listinfo/linux-ia64
prev parent reply other threads:[~2002-06-05 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 7:45 [Linux-ia64] Question about wbinvd Takanori Kawano
2002-06-04 12:02 ` Matthew Wilcox
2002-06-04 17:13 ` Grover, Andrew
2002-06-04 18:36 ` David Mosberger
2002-06-05 5:33 ` Takanori Kawano [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=marc-linux-ia64-105590701905639@msgid-missing \
--to=t-kawano@ebina.hitachi.co.jp \
--cc=linux-ia64@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox