linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Neuling <michael.neuling@au.ibm.com>
To: Frederic Barrat <fbarrat@linux.vnet.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:38:50 +1100	[thread overview]
Message-ID: <1453423130.4239.51.camel@au.ibm.com> (raw)
In-Reply-To: <56A12814.5080607@linux.vnet.ibm.com>

On Thu, 2016-01-21 at 19:48 +0100, Frederic Barrat wrote:
>=20
> Le 20/01/2016 03:20, Michael Neuling a =C3=A9crit :
> > 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.
>=20
> There are actually very few operations we can do on the adapter with=20
> hcalls. papr defines 'reset', 'read the VPD' and flashing a new image on=
=20
> the card. So we'll soon run out of APIs to mimic.
>=20
> I guess it means the usage of cxl_get_phys_dev() should be discouraged,=
=20
> since it's going to lead to different behaviors between bare-metal and=
=20
> powerVM guest. Was there another expected use case for a kernel driver=
=20
> 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.

Thanks again.

Mikey

  reply	other threads:[~2016-01-22  0:38 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 [this message]
2016-01-22 10:56       ` Frederic Barrat
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=1453423130.4239.51.camel@au.ibm.com \
    --to=michael.neuling@au.ibm.com \
    --cc=fbarrat@linux.vnet.ibm.com \
    --cc=ian@ozlabs.au.ibm.com \
    --cc=linuxppc-dev@ozlabs.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).