qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH qemu v7 0/5] spapr: Kill SLOF
Date: Thu, 27 Feb 2020 07:35:09 +0100	[thread overview]
Message-ID: <8063379b-1e02-6e46-0657-72c1e0895235@redhat.com> (raw)
In-Reply-To: <34b5114d-1023-dc01-dd1b-5019c2da47db@ozlabs.ru>

On 27/02/20 00:38, Alexey Kardashevskiy wrote:
> 
> 
> On 26/02/2020 22:34, Paolo Bonzini wrote:
>> On 26/02/20 00:58, Alexey Kardashevskiy wrote:
>>>
>>>
>>> On 21/02/2020 19:27, Paolo Bonzini wrote:
>>>> On 21/02/20 01:18, Alexey Kardashevskiy wrote:
>>>>> I am not quite sure I understood the request.  Write my own small
>>>>> firmware and replace GRUB with it? The firmware from 5/5 reads first 2
>>>>> sectors and the entire PReP, I could add there stuff if that helps (I
>>>>> have "work in progress" patch for the firmware with printk/etc borrowed
>>>>> from SLOF).
>>>>
>>>> Okay, that's great!  I'll take a look next week.
>>>
>>> Just to make sure I understood - you'll take a look on this series, you
>>> do not expect other patches on top, right?
>>
>> No, thanks.
>>
>>> ps. while I have your attention, what was the practical reason for
>>> including capstone to QEMU? Thanks,
>>
>> Newer versions of the binutils disassembler are GPLv3.
> 
> but why does qemu need this kind of disassembler at all? tcg does
> execution and it is not replaced by capstone.

For debugging (e.g. "x/5i $pc" from the monitor, or "-d in_asm" if
you're using TCG).

Paolo



  reply	other threads:[~2020-02-27  6:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20  6:16 [PATCH qemu v7 0/5] spapr: Kill SLOF Alexey Kardashevskiy
2020-02-20  6:16 ` [PATCH qemu v7 1/5] ppc/spapr: Move GPRs setup to one place Alexey Kardashevskiy
2020-02-20  6:16 ` [PATCH qemu v7 2/5] spapr/spapr: Make vty_getchars public Alexey Kardashevskiy
2020-02-20  6:16 ` [PATCH qemu v7 3/5] spapr/cas: Separate CAS handling from rebuilding the FDT Alexey Kardashevskiy
2020-02-20  6:16 ` [PATCH qemu v7 4/5] spapr: Implement Open Firmware client interface Alexey Kardashevskiy
2020-02-20  6:16 ` [PATCH qemu v7 5/5] spapr/vof: Add basic support for MBR/GPT/GRUB Alexey Kardashevskiy
2020-02-20 10:01 ` [PATCH qemu v7 0/5] spapr: Kill SLOF Paolo Bonzini
2020-02-21  0:18   ` Alexey Kardashevskiy
2020-02-21  8:27     ` Paolo Bonzini
2020-02-25 23:58       ` Alexey Kardashevskiy
2020-02-26 11:34         ` Paolo Bonzini
2020-02-26 23:38           ` Alexey Kardashevskiy
2020-02-27  6:35             ` Paolo Bonzini [this message]
2020-03-06  1:17               ` Alexey Kardashevskiy
2020-03-06  8:25                 ` Paolo Bonzini

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=8063379b-1e02-6e46-0657-72c1e0895235@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).