From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH v2] spapr: populate ibm,loc-code
Date: Mon, 30 Mar 2015 14:08:17 +1100 [thread overview]
Message-ID: <5518BE21.6030702@ozlabs.ru> (raw)
In-Reply-To: <20150330022516.GC9908@voom.fritz.box>
On 03/30/2015 01:25 PM, David Gibson wrote:
> On Mon, Mar 30, 2015 at 01:18:01PM +1100, Alexey Kardashevskiy wrote:
>> On 03/27/2015 08:49 PM, Nikunj A Dadhania wrote:
>>> Each hardware instance has a platform unique location code. The OF
>>> device tree that describes a part of a hardware entity must include
>>> the “ibm,loc-code” property with a value that represents the location
>>> code for that hardware entity.
>>>
>>> Introduce an hcall to populate ibm,loc-code.
>>> 1) PCI passthru devices need to identify with its own ibm,loc-code
>>> available on the host.
>>> 2) Emulated devices encode as following: qemu_<name>:<slot>.<fn>
>>>
>>> Signed-off-by: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
> [snip]
>>> diff --git a/include/hw/ppc/spapr.h b/include/hw/ppc/spapr.h
>>> index af71e8b..95157ac 100644
>>> --- a/include/hw/ppc/spapr.h
>>> +++ b/include/hw/ppc/spapr.h
>>> @@ -310,7 +310,10 @@ typedef struct sPAPREnvironment {
>>> #define KVMPPC_H_LOGICAL_MEMOP (KVMPPC_HCALL_BASE + 0x1)
>>> /* Client Architecture support */
>>> #define KVMPPC_H_CAS (KVMPPC_HCALL_BASE + 0x2)
>>> -#define KVMPPC_HCALL_MAX KVMPPC_H_CAS
>>> +#define KVMPPC_H_RTAS_UPDATE (KVMPPC_HCALL_BASE + 0x3)
>>> +#define KVMPPC_H_REPORT_MC_ERR (KVMPPC_HCALL_BASE + 0x4)
>>> +#define KVMPPC_H_GET_LOC_CODE (KVMPPC_HCALL_BASE + 0x5)
>>> +#define KVMPPC_HCALL_MAX KVMPPC_H_GET_LOC_CODE
>>
>>
>> Please add only relevant codes. And what happened to patches adding
>> H_RTAS_UPDATE and H_REPORT_MC_ERR?
>>
>> Also (it is probably a very stupid question but still :) ), why are all
>> these callbacks - hypercalls, not RTAS calls? The hypercalls are numbered in
>> sPAPR and we kind of stealing numbers from that space while we are
>> allocating RTAS tokens ourselves and have more freedom.
>
> Also, I thought the plan was to remove PCI device enumeration from
> SLOF and move it to qemu (since we need to partially do that for
> hotplug). That removes the need for the hcall entirely.
There was a strong opposition to PCI scan done by QEMU (although it was ok
if PCI hotplug does some resource assignment in QEMU). Has this changed?
I added Michael in cc: and hope Alexander may enlighten us on this topic...
--
Alexey
next prev parent reply other threads:[~2015-03-30 3:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 9:49 [Qemu-devel] [PATCH v2] spapr: populate ibm,loc-code Nikunj A Dadhania
2015-03-30 2:18 ` Alexey Kardashevskiy
2015-03-30 2:25 ` David Gibson
2015-03-30 3:08 ` Alexey Kardashevskiy [this message]
2015-03-31 17:52 ` Michael Roth
2015-04-01 5:10 ` Nikunj A Dadhania
2015-03-30 5:02 ` Nikunj A Dadhania
2015-03-30 5:34 ` [Qemu-devel] [Qemu-ppc] [PATCH v2] spapr: populate ibm, loc-code Nikunj A Dadhania
2015-03-30 7:12 ` Alexey Kardashevskiy
2015-03-30 8:22 ` Nikunj A Dadhania
2015-03-30 4:58 ` [Qemu-devel] [PATCH v2] spapr: populate ibm,loc-code Nikunj A Dadhania
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=5518BE21.6030702@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=mdroth@linux.vnet.ibm.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).