All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Clemens Kolbitsch <kolbitsch@lastline.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] FPU x86 instructions error
Date: Sun, 26 May 2013 16:54:26 +0200	[thread overview]
Message-ID: <51A22222.2030409@suse.de> (raw)
In-Reply-To: <519FDF35.207@redhat.com>

Hi,

Am 24.05.2013 23:44, schrieb Paolo Bonzini:
> Il 24/05/2013 23:39, Clemens Kolbitsch ha scritto:
>> we recently had an issue with running a program using FPU instructions
>> to obtain the current EIP (basically a weird way of "call 0; pop eax")
>> that was not working on QEMU (with TCG).
>>
>> Looking at the problem, we found this patch to be useful/fixing the issue:
>>
>> https://launchpadlibrarian.net/140457932/patch-qemu-1.5.0-fpip.diff
>>
>> Looking through the DEVEL archives, I found this patch
>>
>> http://lists.nongnu.org/archive/html/qemu-devel/2011-06/msg01206.html
>>
>> that adds the FPU flags to the environment, but is only using them for KVM.
>>
>> I was wondering - since the above patch is rather old, you have
>> probably come across it before - if there was a reason for not
>> including it in QEMU (I checked in git:master and it's not applied).
>> If there isn't, maybe it'd be worth re-considering :)
> 
> For the TCG patch, there is no Signed-off-by and using a helper is not
> necessary.

Clemens, generally we can't just take another person's patch and apply
it - that's what we need the Signed-off-by for. Your post is the only
Google hit for that link and no hits for fpip in my archive - you'll
need to contact the author to obtain her Sob and properly submit it to
qemu-devel - or post a patch yourself that is not based on that one.

http://wiki.qemu.org/Contribute/SubmitAPatch

> For the KVM patch, it simply fell through the cracks, I believe.

It didn't:
http://git.qemu.org/?p=qemu.git;a=commit;h=42cc8fa620cbc73e349e96d84cf46469e828ec34

(I was about to suggest placing the non-TCG fields into X86CPU. :))

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-05-26 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 21:39 [Qemu-devel] FPU x86 instructions error Clemens Kolbitsch
2013-05-24 21:44 ` Paolo Bonzini
2013-05-26 14:54   ` Andreas Färber [this message]
2013-05-27  0:08     ` Clemens Kolbitsch
2013-05-27  1:17 ` TeLeMan

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=51A22222.2030409@suse.de \
    --to=afaerber@suse.de \
    --cc=kolbitsch@lastline.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.