From: Avi Kivity <avi@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: kvm@vger.kernel.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: Current KVM head crashes on startup
Date: Wed, 18 Feb 2009 12:29:55 +0000 [thread overview]
Message-ID: <499BFF43.4060105@redhat.com> (raw)
In-Reply-To: <20090218122016.GA5955@amit-x200.pnq.redhat.com>
Amit Shah wrote:
>> I don't recall, it probably depends on whether frame pointers are used
>> or not as well.
>>
>
> As far as I know, kvm-userspace build arguments have remained the same
> for quite some time. Also, we still pass the -g flag for userspace
> compilations.
>
>
Some distros change CFLAGS.
>>> -- maintaining
>>> specific code can introduce such regressions.
>>>
>>>
>> That's a problem with assembly. x86 and x86_64 are different
>> instruction sets.
>>
>
> But the code in question isn't different on the two architectures. Just
> a cpuid call that hasn't changed.
>
>
The amount of available registers is different, as is the specification
of which registers may be clobbered.
> OK, given a patch to have just one version of the cpuid call, would you
> be willing to take the risk of finding out which users it breaks for?
> I'll send patches to revert and restore correct behaviour for 32-bit if
> that does happen.
>
This is in upstream qemu so it's not my call but I wouldn't recommend
breaking the build when a trivial one liner is possible.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-02-18 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 17:47 Current KVM head crashes on startup Brian Kress
2009-02-18 7:51 ` Amit Shah
2009-02-18 8:16 ` Amit Shah
2009-02-18 8:49 ` Avi Kivity
2009-02-18 9:05 ` Amit Shah
2009-02-18 10:19 ` Avi Kivity
2009-02-18 11:21 ` Amit Shah
2009-02-18 11:26 ` Avi Kivity
2009-02-18 12:20 ` Amit Shah
2009-02-18 12:29 ` Avi Kivity [this message]
2009-02-18 17:03 ` Avi Kivity
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=499BFF43.4060105@redhat.com \
--to=avi@redhat.com \
--cc=amit.shah@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.