qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH] xics: Don't call icp_kvm_realize() from icp_realize()
Date: Mon, 17 Jun 2019 15:59:49 +0200	[thread overview]
Message-ID: <20190617155949.3ad75f15@bahia.lan> (raw)
In-Reply-To: <97e49445-5d99-f37d-24a1-595123fa00f1@kaod.org>

On Mon, 17 Jun 2019 15:46:14 +0200
Cédric Le Goater <clg@kaod.org> wrote:

> On 17/06/2019 15:25, Greg Kurz wrote:
> > kvm_kernel_irqchip is set by xics_kvm_init() which is always called after
> > icp_realize() since commit 3f777abc7107 "spapr/irq: add KVM support to the
> > 'dual' machine".  
> 
> I think we still need it for CPU hotplug.
> 

Yes you're right of course... a comment would probably help

> C.
> 
> 
> > This is thus dead code. Drop it.
> > 
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> >  hw/intc/xics.c |    8 --------
> >  1 file changed, 8 deletions(-)
> > 
> > diff --git a/hw/intc/xics.c b/hw/intc/xics.c
> > index 29f7d397813e..1dc3a0f12280 100644
> > --- a/hw/intc/xics.c
> > +++ b/hw/intc/xics.c
> > @@ -351,14 +351,6 @@ static void icp_realize(DeviceState *dev, Error **errp)
> >          return;
> >      }
> >  
> > -    if (kvm_irqchip_in_kernel()) {
> > -        icp_kvm_realize(dev, &err);
> > -        if (err) {
> > -            error_propagate(errp, err);
> > -            return;
> > -        }
> > -    }
> > -
> >      qemu_register_reset(icp_reset_handler, dev);
> >      vmstate_register(NULL, icp->cs->cpu_index, &vmstate_icp_server, icp);
> >  }
> >   
> 



      reply	other threads:[~2019-06-17 14:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 13:25 [Qemu-devel] [PATCH] xics: Don't call icp_kvm_realize() from icp_realize() Greg Kurz
2019-06-17 13:46 ` Cédric Le Goater
2019-06-17 13:59   ` Greg Kurz [this message]

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=20190617155949.3ad75f15@bahia.lan \
    --to=groug@kaod.org \
    --cc=clg@kaod.org \
    --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).