From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH]bug fix for softmmu slow_st unaligned access
Date: Sat, 17 Nov 2007 10:54:32 +0100 [thread overview]
Message-ID: <fb249edb0711170154uc6f2few3b19a1e70799658d@mail.gmail.com> (raw)
In-Reply-To: <13502111.post@talk.nabble.com>
Hi,
On 31/10/2007, TeLeMan <geleman@gmail.com> wrote:
> If the 0x10008000 page is writable and 0x10007FFF isn't, softmmu can raise
> this exception before modifing 0x10007FFF-0x10008002 because softmmu checks
> 0x10007FFF at first. I don't know if reversing the order is an exact
> solution,but its simple and working.
Assuming that DATA_SIZE is less than page size, I think it is okay for
a workaround, I committed it. It shows that permissions are checked
two times for the first byte (0x10007ffff) but maybe that's okay since
this is a slow access anyway.
Regards
prev parent reply other threads:[~2007-11-17 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 4:00 [Qemu-devel] [PATCH]bug fix for softmmu slow_st unaligned access TeLeMan
2007-10-31 2:16 ` andrzej zaborowski
2007-10-31 2:59 ` TeLeMan
2007-11-17 9:54 ` andrzej zaborowski [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=fb249edb0711170154uc6f2few3b19a1e70799658d@mail.gmail.com \
--to=balrogg@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).