From: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
To: Michael Neuling <michael.neuling@au1.ibm.com>,
ian@ozlabs.au.ibm.com, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] cxl: Add cxl_read_adapter_vpd() to the kernel API
Date: Fri, 22 Jan 2016 11:56:35 +0100 [thread overview]
Message-ID: <56A20AE3.5060709@linux.vnet.ibm.com> (raw)
In-Reply-To: <1453423130.4239.51.camel@au.ibm.com>
Le 22/01/2016 01:38, Michael Neuling a écrit :
> On Thu, 2016-01-21 at 19:48 +0100, Frederic Barrat wrote:
>>
>> Le 20/01/2016 03:20, Michael Neuling a écrit :
>>> The only thing I'm a bit concerned about is are we going to end up
>>> duplicating a lot of the linux PCI API, but I guess we are only going
>>> to do this for things the papr HCALL interface mimics.
>>
>> There are actually very few operations we can do on the adapter with
>> hcalls. papr defines 'reset', 'read the VPD' and flashing a new image on
>> the card. So we'll soon run out of APIs to mimic.
>>
>> I guess it means the usage of cxl_get_phys_dev() should be discouraged,
>> since it's going to lead to different behaviors between bare-metal and
>> powerVM guest. Was there another expected use case for a kernel driver
>> other than accessing the VPD?
>
> It was just for VPD. I figured it was the easiest way to add it. Maybe
> it's worth getting rid of it in favour of VPD only.
>
> If you want to remove it I'd be happy, but you'll need to coordinate
> with the cxlflash driver. You can probably just write the patch for
> them and then get their ACK on it.
Ok, then I would also be tempted to remove it. I'll sync with cxlflash
to do so.
Thanks!
Fred
next prev parent reply other threads:[~2016-01-22 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 17:14 [PATCH] cxl: Add cxl_read_adapter_vpd() to the kernel API Frederic Barrat
2016-01-20 0:24 ` Andrew Donnellan
2016-01-20 2:20 ` Michael Neuling
2016-01-21 18:48 ` Frederic Barrat
2016-01-22 0:38 ` Michael Neuling
2016-01-22 10:56 ` Frederic Barrat [this message]
2016-01-20 2:21 ` Ian Munsie
2016-03-04 11:22 ` Frederic Barrat
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=56A20AE3.5060709@linux.vnet.ibm.com \
--to=fbarrat@linux.vnet.ibm.com \
--cc=ian@ozlabs.au.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael.neuling@au1.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).