From: Blue Swirl <blauwirbel@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [Qemu-commits] [COMMIT 059b8b1] KVM: x86: Refactor persistent CPU state
Date: Wed, 1 Jul 2009 23:10:15 +0300 [thread overview]
Message-ID: <f43fc5580907011310i35d9df6ci4ff3224387c2ccab@mail.gmail.com> (raw)
In-Reply-To: <4A4BBFAE.5090401@web.de>
On 7/1/09, Jan Kiszka <jan.kiszka@web.de> wrote:
> Anthony Liguori wrote:
> > Blue Swirl wrote:
> >> On 6/30/09, Anthony Liguori <aliguori@us.ibm.com> wrote:
> >>
> >>> From: Jan Kiszka <jan.kiszka@web.de>
> >>>
> >>> This patch aligns the KVM-related layout and encoding of the CPU state
> >>> to be saved to disk or migrated with qemu-kvm. The major differences
> >>> are
> >>> reordering of fields and a compressed interrupt_bitmap into a single
> >>> number as there can be no more than one pending IRQ at a time.
> >>>
> >>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> >>> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> >>>
> >>
> >>
> >>> + for (i = 0; i < ARRAY_SIZE(env->interrupt_bitmap); i++) {
> >>> + bit = ffsll(env->interrupt_bitmap[i]);
> >>>
> >>
> >> This broke build on platforms without ffsll (Mingw32, *BSDs).
> >>
> >
> > What version of mingw32? Mine seems to have ffsll (gcc 4.4.2).
> >
> > Jan, can you send a patch to fix this?
> >
>
>
> I'm currently checking the mingw situation. I likely missed the warning,
> but it seems to link - looking for the header...
>
> Can anyone comment on the BSD situation? I have no test env for such
> platforms.
Grepping for ffsll in /usr/include does not find anything, there is no
man page either.
We could add a local qemu_ffsll (or qemu_ffs64) to osdep.c or cutils.c.
prev parent reply other threads:[~2009-07-01 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200906300055.n5U0tADj013302@d03av01.boulder.ibm.com>
[not found] ` <f43fc5580907011226p5ffac058n26d3d19b74160567@mail.gmail.com>
[not found] ` <4A4BBE84.9020405@us.ibm.com>
2009-07-01 20:04 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT 059b8b1] KVM: x86: Refactor persistent CPU state Blue Swirl
[not found] ` <4A4BBFAE.5090401@web.de>
2009-07-01 20:10 ` Blue Swirl [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=f43fc5580907011310i35d9df6ci4ff3224387c2ccab@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@web.de \
--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).