* [Qemu-devel] Re: [Qemu-commits] [COMMIT 059b8b1] KVM: x86: Refactor persistent CPU state
[not found] ` <4A4BBE84.9020405@us.ibm.com>
@ 2009-07-01 20:04 ` Blue Swirl
[not found] ` <4A4BBFAE.5090401@web.de>
1 sibling, 0 replies; 2+ messages in thread
From: Blue Swirl @ 2009-07-01 20:04 UTC (permalink / raw)
To: Anthony Liguori; +Cc: Jan Kiszka, qemu-devel
On 7/1/09, Anthony Liguori <aliguori@us.ibm.com> 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).
Using built-in specs.
Target: i586-mingw32msvc
Configured with:
/home/ron/devel/debian/mingw32/mingw32-4.2.1.dfsg/build_dir/src/gcc-4.2.1-2-dfsg/configure
-v --prefix=/usr --target=i586-mingw32msvc --enable-languages=c,c++
--enable-threads --enable-sjlj-exceptions --disable-multilib
--enable-version-specific-runtime-libs
Thread model: win32
gcc version 4.2.1-sjlj (mingw32-2)
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Qemu-devel] Re: [Qemu-commits] [COMMIT 059b8b1] KVM: x86: Refactor persistent CPU state
[not found] ` <4A4BBFAE.5090401@web.de>
@ 2009-07-01 20:10 ` Blue Swirl
0 siblings, 0 replies; 2+ messages in thread
From: Blue Swirl @ 2009-07-01 20:10 UTC (permalink / raw)
To: Jan Kiszka; +Cc: Anthony Liguori, qemu-devel
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-07-01 20:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 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).