From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] How drivers notice a MCA on I/O read? [1/3]
Date: Tue, 25 Nov 2003 09:27:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106975273502760@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106915044130197@msgid-missing>
Thanks, all.
For the moment, what I mentioned was only about I/O read interface between
drivers and MCA handler, and as Zoltan mentioned, something like recovering
from each
I/O read
I/O write
DMA from memory to device
DMA from device to memory
is still left as problem to be solved. I'm glad to hear some comment about this.
Well, I'd try to carry out the codes that really consume the data without
leaning mf.a. (Since I'm not familiar with IA64 machine instruction now,
maybe it takes a long time...)
And also, I'd try to check the difference between the readb_check and usual
readb. I should reconsider my attempt if the considerable overhead exists.
Surely, readb_check concerns the interface for drivers, so I think it is better
to consider my plan of discussion on linux-kernel@vger.kern.org.
------
H.Seto <seto.hidetoshi@jp.fujitsu.com>
prev parent reply other threads:[~2003-11-25 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 10:11 [RFC] How drivers notice a MCA on I/O read? [1/3] Hidetoshi Seto
2003-11-18 10:12 ` [RFC] How drivers notice a MCA on I/O read? [2/3] Hidetoshi Seto
2003-11-18 10:14 ` [RFC] How drivers notice a MCA on I/O read? [3/3] Hidetoshi Seto
2003-11-18 15:06 ` [RFC] How drivers notice a MCA on I/O read? [1/3] Zoltan Menyhart
2003-11-18 17:10 ` Jesse Barnes
2003-11-18 17:47 ` Luck, Tony
2003-11-19 16:45 ` Grant Grundler
2003-11-25 9:27 ` Hidetoshi Seto [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-106975273502760@msgid-missing \
--to=seto.hidetoshi@jp.fujitsu.com \
--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