From: Paolo Bonzini <pbonzini@redhat.com>
To: Frediano Ziglio <freddy77@gmail.com>,
Anthony Liguori <aliguori@amazon.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: Frediano Ziglio <frediano.ziglio@huawei.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] qemu-common.h: optimise muldiv64 for x86_64 architecture
Date: Fri, 09 Jan 2015 12:43:55 +0100 [thread overview]
Message-ID: <54AFBEFB.6000204@redhat.com> (raw)
In-Reply-To: <1420802721-14457-2-git-send-email-frediano.ziglio@huawei.com>
On 09/01/2015 12:25, Frediano Ziglio wrote:
> /* compute with 96 bit intermediate result: (a*b)/c */
> -#ifdef CONFIG_INT128
> +#if defined(CONFIG_INT128) && !defined(__x86_64__)
> static inline uint64_t muldiv64(uint64_t a, uint32_t b, uint32_t c)
> {
> return (__int128)a * b / c;
> }
> +#elif defined(__x86_64__)
> +/* Optimised x64 version. This assume that a*b/c fits in 64 bit */
> +static inline uint64_t muldiv64(uint64_t a, uint32_t b, uint32_t c)
> +{
> + uint64_t res;
> +
> + asm ("mulq %2\n\tdivq %3"
> + : "=a"(res)
> + : "a"(a), "qm"((uint64_t) b), "qm"((uint64_t)c)
> + : "rdx", "cc");
> + return res;
> +}
Reorder it the other way, and you can simplify the first #if.
I applied patch 1 locally, and will send a pull request once the tree is
thawed.
Paolo
next prev parent reply other threads:[~2015-01-09 11:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 11:25 [Qemu-devel] [PATCH 1/2] qemu-common.h: optimise muldiv64 if int128 is available Frediano Ziglio
2015-01-09 11:25 ` [Qemu-devel] [PATCH 2/2] qemu-common.h: optimise muldiv64 for x86_64 architecture Frediano Ziglio
2015-01-09 11:43 ` Paolo Bonzini [this message]
2015-01-09 12:09 ` Frediano Ziglio
2015-01-09 12:22 ` Peter Maydell
2015-01-09 15:41 ` Frediano Ziglio
2015-01-09 15:52 ` Peter Maydell
2015-01-09 16:08 ` Frediano Ziglio
2015-01-09 16:10 ` Peter Maydell
2015-01-09 12:03 ` [Qemu-devel] [PATCH 1/2] qemu-common.h: optimise muldiv64 if int128 is available Peter Maydell
2015-01-09 13:43 ` Frediano Ziglio
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=54AFBEFB.6000204@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@amazon.com \
--cc=freddy77@gmail.com \
--cc=frediano.ziglio@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).