From: christophe lombard <clombard@linux.vnet.ibm.com>
To: benh@au1.ibm.com, linuxppc-dev@lists.ozlabs.org,
fbarrat@linux.vnet.ibm.com, vaibhav@linux.vnet.ibm.com,
andrew.donnellan@au1.ibm.com
Subject: Re: [PATCH] cxl: Add support for ASB_Notify on POWER9
Date: Fri, 24 Nov 2017 17:37:35 +0100 [thread overview]
Message-ID: <d18c47e1-d40f-1d6e-e68c-99ae7be01737@linux.vnet.ibm.com> (raw)
In-Reply-To: <1511528547.2466.52.camel@au1.ibm.com>
Le 24/11/2017 à 14:02, Benjamin Herrenschmidt a écrit :
> On Fri, 2017-11-24 at 11:14 +0100, christophe lombard wrote:
>> To my knowledge, there is no property (or similar), somewhere, that
>> indicating that the TIDR is supported or not.
>> For the time being, if I am not wrong, the only check we have, is
>> this condition in the function set_thread_tidr(struct task_struct *t):
>>
>> if (!cpu_has_feature(CPU_FTR_ARCH_300))
>> return -EINVAL;
>>
>>
>> Christophe
>
> Then we need to fix that
>
> Ben.
>
You are right. We will insert a checking in the cxl driver to allow
updating the TIDR if a P9 is present. This will be in the patch V2.
Thanks
Christophe
next prev parent reply other threads:[~2017-11-24 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 11:05 [PATCH] cxl: Add support for ASB_Notify on POWER9 Christophe Lombard
2017-11-23 14:16 ` Vaibhav Jain
2017-11-23 16:15 ` christophe lombard
2017-11-23 20:41 ` Benjamin Herrenschmidt
2017-11-24 10:14 ` christophe lombard
2017-11-24 13:02 ` Benjamin Herrenschmidt
2017-11-24 16:37 ` christophe lombard [this message]
2017-11-24 19:54 ` Benjamin Herrenschmidt
2017-11-27 4:03 ` Michael Ellerman
2017-11-27 10:17 ` christophe lombard
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=d18c47e1-d40f-1d6e-e68c-99ae7be01737@linux.vnet.ibm.com \
--to=clombard@linux.vnet.ibm.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=benh@au1.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=vaibhav@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).