From: "Michael S. Tsirkin" <mst@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Stefan Weil <sw@weilnetz.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH master/stable-1.0] pci: fix corrupted pci conf index register by unaligned write
Date: Sun, 8 Jan 2012 14:45:17 +0200 [thread overview]
Message-ID: <20120108124516.GC26189@redhat.com> (raw)
In-Reply-To: <4F097465.8090103@redhat.com>
On Sun, Jan 08, 2012 at 12:48:05PM +0200, Avi Kivity wrote:
> On 01/08/2012 12:12 PM, Michael S. Tsirkin wrote:
> > > >
> > > > > And the check for unaligned writes is, well, unusual :-)
> > >
> > > What's unusual?
> > >
> > >
> > > > This seems to be how memory API behaves ... right, Avi?
> > > > Maybe this should be documented somewhere.
> > >
> > > Document what?
> >
> > That address passed to callbacks is in fact an offset
> > from start of the region.
> >
>
> It's documented already (and it's not new - since 8da3ff18097, Dec 2008).
True, memory.h explicitly says:
@addr is relative to @mr
But now that's mentioned, I have a question:
we could also specify min access size and disable
unaligned access in ops.valid structure.
That would trigger machine checks on access errors
instead of ignoring them as we do now.
Anyone knows offhand what does real hardware do?
> --
> error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-01-08 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 14:28 [Qemu-devel] [PATCH master/stable-1.0] pci: fix corrupted pci conf index register by unaligned write Avi Kivity
2012-01-04 14:47 ` Michael S. Tsirkin
2012-01-04 15:34 ` Alexander Graf
2012-01-05 15:14 ` Stefan Weil
2012-01-08 9:17 ` Michael S. Tsirkin
2012-01-08 10:02 ` Avi Kivity
2012-01-08 10:12 ` Michael S. Tsirkin
2012-01-08 10:48 ` Avi Kivity
2012-01-08 12:45 ` Michael S. Tsirkin [this message]
2012-01-08 12:53 ` Avi Kivity
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=20120108124516.GC26189@redhat.com \
--to=mst@redhat.com \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.