All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] target/i386: Implement all TBM instructions
Date: Wed, 12 Jul 2017 08:43:07 -1000	[thread overview]
Message-ID: <66a7981d-4938-eea9-ef7a-c7622596eaf6@twiddle.net> (raw)
In-Reply-To: <CAPybu_0+enKVGf-bZHrkvWQ8reFtJnkKC=sucr2aaZ_DidaHNA@mail.gmail.com>

On 07/12/2017 03:28 AM, Ricardo Ribalda Delgado wrote:
> Hi Richard
> 
> Thanks for your patch! I have applied it to my tree, but i still get
> SIGSEGV. I think that I might have found the problem. It seems to be
> related to the bmi instruction blsr, which seems to be not properly
> implemented.

You're absolutely right.


r~

  reply	other threads:[~2017-07-12 18:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 21:21 [Qemu-devel] [PATCH 0/2] target/i386: Implement all TBM instructions Richard Henderson
2017-07-11 21:21 ` [Qemu-devel] [PATCH 1/2] target/i386: Decode AMD XOP prefix Richard Henderson
2017-07-11 21:21 ` [Qemu-devel] [PATCH 2/2] target/i386: Implement all TBM instructions Richard Henderson
2017-07-12  4:04 ` [Qemu-devel] [PATCH 0/2] " Richard Henderson
2017-07-12 13:28   ` Ricardo Ribalda Delgado
2017-07-12 18:43     ` Richard Henderson [this message]
2017-07-12 18:45     ` [Qemu-devel] [PATCH] target/i386: Fix BLSR and BLSI Richard Henderson
2017-07-12 18:58       ` Ricardo Ribalda Delgado
2017-07-12 19:12         ` Richard Henderson
2017-07-12 19:25           ` Ricardo Ribalda Delgado
2018-06-06  9:13       ` Ricardo Ribalda Delgado
2018-06-06 12:32         ` Paolo Bonzini
2017-07-12 19:29     ` [Qemu-devel] [PATCH v2] " Richard Henderson
2017-07-13 20:42       ` Ricardo Ribalda Delgado
2017-07-13 21:55         ` Ricardo Ribalda Delgado
2017-07-13 22:49           ` Ricardo Ribalda Delgado

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=66a7981d-4938-eea9-ef7a-c7622596eaf6@twiddle.net \
    --to=rth@twiddle.net \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ricardo.ribalda@gmail.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 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.