From: Julian Stecklina <js@alien8.de>
To: KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: IOAPIC doesn't handle byte writes
Date: Tue, 22 Nov 2011 16:06:51 +0100 [thread overview]
Message-ID: <1321974411.16507.25.camel@tabernacle.lan> (raw)
Hello,
Avi Kivity wrote:
> Care to post a patch instead?
Sure. Never hacked KVM, though. Is there a particular reason why the
void *val argument to ioapic_mmio_read/_write is only dereferenced when
ioapic->lock is not held?
Regards, Julian
next reply other threads:[~2011-11-22 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 15:06 Julian Stecklina [this message]
2011-11-23 10:45 ` IOAPIC doesn't handle byte writes Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2011-11-22 13:13 Julian Stecklina
2011-11-22 14:19 ` Avi Kivity
2011-12-04 9:53 ` Gleb Natapov
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=1321974411.16507.25.camel@tabernacle.lan \
--to=js@alien8.de \
--cc=kvm@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;
as well as URLs for NNTP newsgroup(s).