From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [5849] Change MMIO callbacks to use offsets, not absolute addresses.
Date: Thu, 26 Feb 2009 15:19:42 +0000 [thread overview]
Message-ID: <200902261519.44234.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580902251154r92cff22ufb1636a21ea5c0e4@mail.gmail.com>
> > You either have to explicitly sync state (In teh case of SPARC this
> > means saving PC and NPC), or you have to know about the fault in the
> > low-level TLB processing code where you still have enough information to
> > recover this information. Once you get into an IO handler you've no way
> > of figuring out what the current CPU state is. The "not in all
> > cases"/"some faults" you mention above is relatively rare instructions
> > that may fault v.s. every memory access.
>
> Well, until r4431 we always saved PC and NPC for all memory access
> instructions, but with that commit, some of the checks could be
> removed and everything still work.
I don't believe that everything still works. Alignemnt checks work because
they are enfored by the low-level TLB code. I'm pretty sure unassigned access
faults are broken.
Paul
prev parent reply other threads:[~2009-02-26 15:19 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
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 [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=200902261519.44234.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=blauwirbel@gmail.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).