public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Radim Krčmář" <rkrcmar@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	Paul Mackerras <paulus@samba.org>,
	Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] powerpc: move hmi.c to arch/powerpc/kvm/
Date: Thu, 11 Aug 2016 12:03:32 +1000	[thread overview]
Message-ID: <87vaz8t62z.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20160810184127.GA27257@potion>

Radim Krčmář <rkrcmar@redhat.com> writes:

> 2016-08-03 13:36+0200, Paolo Bonzini:
>> hmi.c functions are unused unless sibling_subcore_state is nonzero, and
>> that in turn happens only if KVM is in use.  So move the code to
>> arch/powerpc/kvm/, putting it under CONFIG_KVM_BOOK3S_64_HANDLER
>> rather than CONFIG_PPC_BOOK3S_64.  The sibling_subcore_state is also
>> included in struct paca_struct only if KVM is supported by the kernel.
>> 
>> Cc: Paul Mackerras <paulus@samba.org>
>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>> Cc: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
>> Cc: linuxppc-dev@lists.ozlabs.org
>> Cc: kvm-ppc@vger.kernel.org
>> Cc: kvm@vger.kernel.org
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> 	It would be nice to have this in 4.8, to minimize any 4.9 conflicts.
>> 	Build-tested only, with and without KVM enabled.
>
> If you agree with the change, would you prefer to have this patch merged
> through the PowerPC tree?

Yeah I'll pull it into my fixes branch.

cheers

  reply	other threads:[~2016-08-11  2:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03 11:36 [PATCH] powerpc: move hmi.c to arch/powerpc/kvm/ Paolo Bonzini
2016-08-04  2:17 ` Daniel Axtens
2016-08-10 18:41 ` Radim Krčmář
2016-08-11  2:03   ` Michael Ellerman [this message]
2016-08-11 11:07     ` Michael Ellerman

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=87vaz8t62z.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mahesh@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox