From: Takanori Kawano <t-kawano@ebina.hitachi.co.jp>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Question about wbinvd
Date: Tue, 04 Jun 2002 07:45:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905635@msgid-missing> (raw)
Hello,
I have a question about wbinvd in acpi code.
In 2.4.18, wbinvd is implemented in drivers/acpi/include/platform/acgcc.h
as follows.
static inline void
wbinvd (void)
{
unsigned long flags, vector, position = 0;
long status;
do {
ia64_clear_ic(flags);
status = ia64_pal_cache_flush(0x3, (PAL_CACHE_FLUSH_INVALIDATE
| PAL_CACHE_FLUSH_CHK_INTRS)
,
&position, &vector);
local_irq_restore(flags);
if (status = 1) {
ia64_eoi();
hw_resend_irq(NULL, vector);
}
} while (status = 1);
}
I think it may cause infinite loop if PAL_CACHE_FLUSH continues to
exit for a pending interrupt without flushing any lines.
Is it correct to call hw_resend_irq as is?
regards,
---
Takanori Kawano
Hitachi Ltd,
Internet Systems Platform Division
t-kawano@ebina.hitachi.co.jp
next reply other threads:[~2002-06-04 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 7:45 Takanori Kawano [this message]
2002-06-04 12:02 ` [Linux-ia64] Question about wbinvd Matthew Wilcox
2002-06-04 17:13 ` Grover, Andrew
2002-06-04 18:36 ` David Mosberger
2002-06-05 5:33 ` Takanori Kawano
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-105590701905635@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