From: Eric Blake <eblake@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>, Greg Kurz <groug@kaod.org>
Cc: qemu-ppc@nongnu.org, "Cédric Le Goater" <clg@kaod.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 01/10] xics: Explicitely call KVM ICP methods from the common code
Date: Mon, 18 Feb 2019 14:10:41 -0600 [thread overview]
Message-ID: <03af3e28-3fdb-50e9-295a-09dededf5af5@redhat.com> (raw)
In-Reply-To: <20190217231455.GB2765@umbus.fritz.box>
On 2/17/19 5:14 PM, David Gibson wrote:
In the subject line: s/Explicitely/Explicitly/
> On Fri, Feb 15, 2019 at 12:39:48PM +0100, Greg Kurz wrote:
>> The pre_save(), post_load() and synchronize_state() methods of the
>> ICPStateClass type are really KVM only things. Make that obvious
>> by dropping the indirections and directly calling the KVM functions
>> instead.
>>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-02-18 20:11 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 11:39 [Qemu-devel] [PATCH 00/10] xics: Get rid of KVM specific classes Greg Kurz
2019-02-15 11:39 ` [Qemu-devel] [PATCH 01/10] xics: Explicitely call KVM ICP methods from the common code Greg Kurz
2019-02-15 12:49 ` Cédric Le Goater
2019-02-17 23:14 ` David Gibson
2019-02-18 20:10 ` Eric Blake [this message]
2019-02-19 5:36 ` David Gibson
2019-02-15 11:39 ` [Qemu-devel] [PATCH 02/10] xics: Handle KVM ICP reset " Greg Kurz
2019-02-15 12:50 ` Cédric Le Goater
2019-02-17 23:32 ` David Gibson
2019-02-15 11:40 ` [Qemu-devel] [PATCH 03/10] xics: Handle KVM ICP realize " Greg Kurz
2019-02-15 12:54 ` Cédric Le Goater
2019-02-15 13:03 ` Greg Kurz
2019-02-15 13:09 ` Cédric Le Goater
2019-02-15 13:27 ` Greg Kurz
2019-02-15 13:35 ` Cédric Le Goater
2019-02-17 23:33 ` David Gibson
2019-02-15 11:40 ` [Qemu-devel] [PATCH 04/10] spapr/irq: Use the base ICP class for KVM Greg Kurz
2019-02-15 12:54 ` Cédric Le Goater
2019-02-17 23:35 ` David Gibson
2019-02-15 11:40 ` [Qemu-devel] [PATCH 05/10] xics: Drop the KVM ICP class Greg Kurz
2019-02-15 12:55 ` Cédric Le Goater
2019-02-15 13:18 ` Greg Kurz
2019-02-15 13:35 ` Cédric Le Goater
2019-02-15 13:35 ` Greg Kurz
2019-02-17 23:37 ` David Gibson
2019-02-18 7:08 ` Cédric Le Goater
2019-02-15 11:40 ` [Qemu-devel] [PATCH 06/10] xics: Explicitely call KVM ICS methods from the common code Greg Kurz
2019-02-15 12:56 ` Cédric Le Goater
2019-02-17 23:39 ` David Gibson
2019-02-15 11:40 ` [Qemu-devel] [PATCH 07/10] xics: Handle KVM ICS reset from the "simple" ICS code Greg Kurz
2019-02-15 12:57 ` Cédric Le Goater
2019-02-17 23:41 ` David Gibson
2019-02-15 11:40 ` [Qemu-devel] [PATCH 08/10] xics: Handle KVM interrupt presentation from " Greg Kurz
2019-02-15 12:59 ` Cédric Le Goater
2019-02-15 13:25 ` Greg Kurz
2019-02-17 23:43 ` David Gibson
2019-02-15 11:40 ` [Qemu-devel] [PATCH 09/10] spapr/irq: Use the "simple" ICS class for KVM Greg Kurz
2019-02-15 13:02 ` Cédric Le Goater
2019-02-15 13:32 ` Greg Kurz
2019-02-15 13:37 ` Cédric Le Goater
2019-02-17 23:49 ` David Gibson
2019-02-17 23:51 ` David Gibson
2019-02-15 11:40 ` [Qemu-devel] [PATCH 10/10] xics: Drop the KVM ICS class Greg Kurz
2019-02-15 13:02 ` Cédric Le Goater
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=03af3e28-3fdb-50e9-295a-09dededf5af5@redhat.com \
--to=eblake@redhat.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--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).