On Mon, Jun 23, 2014 at 06:18:37PM +0200, Alexander Graf wrote:
>
>On 23.06.14 04:22, Gavin Shan wrote:
>>The patch implements PCI error injection RTAS calls for sPAPR
>>platform, which are defined PAPR spec as follows. Those RTAS
>>calls are expected to be invoked in strict sequence of
>>"ibm,open
On Mon, Jun 23, 2014 at 11:13:45PM +0200, Alexander Graf wrote:
>
>> Am 23.06.2014 um 23:03 schrieb Benjamin Herrenschmidt
>> :
>>
>>> On Mon, 2014-06-23 at 18:18 +0200, Alexander Graf wrote:
>>> Device emulation code shouldn't even remotely have an idea what host
>>> it's running on. Also seman
> Am 23.06.2014 um 23:03 schrieb Benjamin Herrenschmidt
> :
>
>> On Mon, 2014-06-23 at 18:18 +0200, Alexander Graf wrote:
>> Device emulation code shouldn't even remotely have an idea what host
>> it's running on. Also semantically there are a few issues with this approach
>>
>> 1) QEMU is
On Mon, 2014-06-23 at 18:18 +0200, Alexander Graf wrote:
> Device emulation code shouldn't even remotely have an idea what host
> it's running on. Also semantically there are a few issues with this approach
>
>1) QEMU is usually running with user privileges, so it doesn't have
> access to th
On 23.06.14 04:22, Gavin Shan wrote:
The patch implements PCI error injection RTAS calls for sPAPR
platform, which are defined PAPR spec as follows. Those RTAS
calls are expected to be invoked in strict sequence of
"ibm,open-errinjct", "ibm,errinjct", "ibm,close-errinjct".
- "ibm,open-errinjct"
The patch implements PCI error injection RTAS calls for sPAPR
platform, which are defined PAPR spec as follows. Those RTAS
calls are expected to be invoked in strict sequence of
"ibm,open-errinjct", "ibm,errinjct", "ibm,close-errinjct".
- "ibm,open-errinjct": Apply for token to do error injection
