From: Bernhard Kohl <bernhard.kohl@gmx.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH][RESEND] exec: optimize lduw_phys and stw_phys
Date: Sun, 09 May 2010 14:36:19 +0200 [thread overview]
Message-ID: <hs6a83$4si$1@dough.gmane.org> (raw)
In-Reply-To: <4BE2CA41.8060701@nsn.com>
Am 06.05.2010 15:55, schrieb Bernhard Kohl:
> Implementation of the optimized code for these two functions.
>
> This is necessary for virtio which reads and writes VirtQueue index
> fields using these functions. The assumption is that this are atomic
> operations, which is not the case, if the memcpy() function which is
> used in the non optimized code does single byte copying. This happens
> for example with an older WindRiver glibc.
>
> Signed-off-by: Bernhard Kohl <bernhard.kohl@nsn.com>
Hi,
the same patch posted by Michael S. Tsirkin was commited one hour
after I sent this message.
topic: [PATCH] qemu: address todo comment in exec.c
commit: 733f0b02c80c3a7106d8327a83948ab68db10ea7
So this issue is closed.
Bernhard
prev parent reply other threads:[~2010-05-09 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 13:55 [Qemu-devel] [PATCH][RESEND] exec: optimize lduw_phys and stw_phys Bernhard Kohl
2010-05-09 12:36 ` Bernhard Kohl [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='hs6a83$4si$1@dough.gmane.org' \
--to=bernhard.kohl@gmx.net \
--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).