From: "Michael S. Tsirkin" <mst@redhat.com>
To: kvm@vger.kernel.org, kvm-ia64@vger.kernel.org, xiantao.zhang@intel.com
Cc: avi@redhat.com
Subject: ia64: why is mmio bus access lockless?
Date: Wed, 24 Jun 2009 18:00:43 +0300 [thread overview]
Message-ID: <20090624150041.GA28496@redhat.com> (raw)
Hi,
arch/ia64/kvm/kvm-ia64.c does this:
mmio_dev = vcpu_find_mmio_dev(vcpu, p->addr, p->size, !p->dir);
if (mmio_dev) {
if (!p->dir)
kvm_iodevice_write(mmio_dev, p->addr, p->size,
&p->data);
else
kvm_iodevice_read(mmio_dev, p->addr, p->size,
&p->data);
without holding kvm lock.
I know that find/read/write on the bus require locking on x86 -
are they safe to do without locking on ia64?
--
MST
next reply other threads:[~2009-06-24 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 15:00 Michael S. Tsirkin [this message]
2009-06-26 1:57 ` ia64: why is mmio bus access lockless? Zhang, Xiantao
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=20090624150041.GA28496@redhat.com \
--to=mst@redhat.com \
--cc=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=xiantao.zhang@intel.com \
/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