All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Balbir Singh <bsingharora@gmail.com>,
	linuxppc-dev@lists.ozlabs.org,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH] powerpc/pseries: Add POWER8NVL support to ibm,client-architecture-support call
Date: Wed, 8 Jun 2016 12:58:00 +0200	[thread overview]
Message-ID: <5757FA38.3030108@redhat.com> (raw)
In-Reply-To: <70305fb4-d345-bd89-e395-04c39b266fe4@gmail.com>

On 08.06.2016 03:14, Balbir Singh wrote:
> 
> On 31/05/16 20:32, Michael Ellerman wrote:
>> On Tue, 2016-05-31 at 12:19 +0200, Thomas Huth wrote:
>>> On 31.05.2016 12:04, Michael Ellerman wrote:
>>>> On Tue, 2016-05-31 at 07:51 +0200, Thomas Huth wrote:
>>>>> If we do not provide the PVR for POWER8NVL, a guest on this
>>>>> system currently ends up in PowerISA 2.06 compatibility mode on
>>>>> KVM, since QEMU does not provide a generic PowerISA 2.07 mode yet.
>>>>> So some new instructions from POWER8 (like "mtvsrd") get disabled
>>>>> for the guest, resulting in crashes when using code compiled
>>>>> explicitly for POWER8 (e.g. with the "-mcpu=power8" option of GCC).
>>>>>
>>>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>>>
>>>> So this should say:
>>>>
>>>>   Fixes: ddee09c099c3 ("powerpc: Add PVR for POWER8NVL processor")
>>>>
>>>> And therefore:
>>>>
>>>>   Cc: stable@vger.kernel.org # v4.0+
>>>>
>>>> Am I right?
>>>
>>> Right. (At least for virtualized systems ... for bare-metal systems,
>>> that original patch was enough). So shall I resubmit my patch with these
>>> two lines, or could you add them when you pick this patch up?
>>
>> Thanks, I'll add them here.
> 
> Don't we need to update IBM_ARCH_VEC_NRCORES_OFFSET as well?

D'oh! You're right, that needs to be changed, too! I'll send a fixup
patch once I've tested it...

By the way, there seems to be already a check for
ibm_architecture_vec[IBM_ARCH_VEC_NRCORES_OFFSET] != NR_CPUS in
prom_send_capabilities(), but it only prints out a warning which easily
gets lost in the kernel log ... I wonder whether we should rather stop
the boot there instead to catch this problem more easily?

 Thomas

  parent reply	other threads:[~2016-06-08 10:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31  5:51 [PATCH] powerpc/pseries: Add POWER8NVL support to ibm,client-architecture-support call Thomas Huth
2016-05-31  5:51 ` [PATCH] powerpc/pseries: Add POWER8NVL support to ibm, client-architecture-support call Thomas Huth
2016-05-31 10:04 ` [PATCH] powerpc/pseries: Add POWER8NVL support to ibm,client-architecture-support call Michael Ellerman
2016-05-31 10:04   ` Michael Ellerman
2016-05-31 10:19   ` Thomas Huth
2016-05-31 10:19     ` Thomas Huth
2016-05-31 10:32     ` Michael Ellerman
2016-05-31 10:32       ` Michael Ellerman
2016-06-08  1:14       ` Balbir Singh
2016-06-08 10:44         ` Michael Ellerman
2016-06-08 11:17           ` Thomas Huth
2016-06-08 11:27             ` Michael Ellerman
2016-06-08 10:58         ` Thomas Huth [this message]
2016-06-06  0:17 ` powerpc/pseries: Add POWER8NVL support to ibm, client-architecture-support call Michael Ellerman
2016-06-06  0:17   ` 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=5757FA38.3030108@redhat.com \
    --to=thuth@redhat.com \
    --cc=bsingharora@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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.