From: Robert Reif <reif@earthlink.net>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5849] Change MMIO callbacks to use offsets, not absolute addresses.
Date: Mon, 23 Feb 2009 20:27:25 -0500 [thread overview]
Message-ID: <49A34CFD.1010506@earthlink.net> (raw)
In-Reply-To: <200902240112.28240.paul@codesourcery.com>
Paul Brook wrote:
>> How do you propose having the hardware drivers generate meaningful and
>> timely faults when an improper access is performed so it behaves like real
>> low level software expects the hardware to behave?
>>
>
> If you're wanting to generate faults from IO devices then getting the right
> physical address is the least of your concerns. First you need to figure out
> how to avoid corrupting the rest of the CPU state.
>
> Paul
>
>
The MMU does it so it must be possible. Is it a design issue, performance
issue, just not worth the trouble or no one has really cared up until now?
Please enlighten me further. Is it reasonable to expect it to work someday
or should I just accept that it won't?
next prev parent reply other threads:[~2009-02-24 1:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 18:59 [Qemu-devel] [5849] Change MMIO callbacks to use offsets, not absolute addresses Paul Brook
2009-02-23 12:18 ` Robert Reif
2009-02-23 12:36 ` Paul Brook
2009-02-23 12:42 ` Robert Reif
2009-02-23 13:16 ` Paul Brook
2009-02-23 16:43 ` Robert Reif
2009-02-23 17:04 ` Paul Brook
2009-02-24 0:08 ` Robert Reif
2009-02-24 0:30 ` Paul Brook
2009-02-24 1:05 ` Robert Reif
2009-02-24 1:12 ` Paul Brook
2009-02-24 1:27 ` Robert Reif [this message]
2009-02-24 1:50 ` Paul Brook
2009-02-24 21:04 ` Blue Swirl
2009-02-24 22:28 ` Paul Brook
2009-02-25 19:54 ` Blue Swirl
2009-02-26 15:19 ` Paul Brook
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=49A34CFD.1010506@earthlink.net \
--to=reif@earthlink.net \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).