Displaying 8 results from an estimated 8 matches for "cper".
Did you mean:
aper
2017 Jun 23
2
Simple control structure issue
...ime with 'next'. I come from the "sloppy" school that learned BASIC with Goto.
Conceptually next seems pretty straightforward. I just can't get it to work correctly in my code. Here's a stripped down version:
WhichRunNow<-"Daily"
Cnums=c(0,1,"2b3")
Cpers=c("Daily","Daily","Weekly")
for (j in (1:length(Cnums))) {
If (!identical(Cpers[j],WhichRunNow)){
next
}
print(j)
}
So, this should print the number "3", which it does. It prints 3 because "WhichRunNow" is "Da...
2017 Jun 23
0
Simple control structure issue
...he "sloppy" school that
> learned BASIC with Goto.
>
> Conceptually next seems pretty straightforward. I just can't get it to
> work correctly in my code. Here's a stripped down version:
>
> WhichRunNow<-"Daily"
> Cnums=c(0,1,"2b3")
> Cpers=c("Daily","Daily","Weekly")
>
> for (j in (1:length(Cnums))) {
> If (!identical(Cpers[j],WhichRunNow)){
> next
> }
> print(j)
> }
>
> So, this should print the number "3", which it does. It prints 3...
2016 Nov 16
2
[PATCH 1/3] virtio: Basic implementation of virtio pstore driver
Hi,
On Tue, Nov 15, 2016 at 11:38 PM, Paolo Bonzini <pbonzini at redhat.com> wrote:
>
>
> On 15/11/2016 15:36, Namhyung Kim wrote:
>> Hi,
>>
>> On Tue, Nov 15, 2016 at 10:57:29AM +0100, Paolo Bonzini wrote:
>>>
>>>
>>> On 15/11/2016 06:06, Michael S. Tsirkin wrote:
>>>> On Tue, Nov 15, 2016 at 01:50:21PM +0900, Namhyung Kim
2016 Nov 16
2
[PATCH 1/3] virtio: Basic implementation of virtio pstore driver
Hi,
On Tue, Nov 15, 2016 at 11:38 PM, Paolo Bonzini <pbonzini at redhat.com> wrote:
>
>
> On 15/11/2016 15:36, Namhyung Kim wrote:
>> Hi,
>>
>> On Tue, Nov 15, 2016 at 10:57:29AM +0100, Paolo Bonzini wrote:
>>>
>>>
>>> On 15/11/2016 06:06, Michael S. Tsirkin wrote:
>>>> On Tue, Nov 15, 2016 at 01:50:21PM +0900, Namhyung Kim
2016 Nov 16
0
[PATCH 1/3] virtio: Basic implementation of virtio pstore driver
> Not sure how independent ERST is from ACPI and other specs. It looks
> like referencing UEFI spec at least.
It is just the format of error records that comes from the UEFI spec
(include/linux/cper.h) but you can ignore it, I think. It should be
handled by tools on the host side. For you, the error log address
range contains a CPER header followed by a binary blob. In practice,
you only need the record length field (bytes 20-23 of the header),
though it may be a good idea to validate the s...
2010 Aug 20
0
[PATCH 1/2] Implement APEI ERST feature to Xen
...i/apei-base.c | 278 +++++++++++
b/xen/drivers/acpi/apei/apei-internal.h | 73 ++
b/xen/drivers/acpi/apei/apei-io.c | 328 +++++++++++++
b/xen/drivers/acpi/apei/erst.c | 787 ++++++++++++++++++++++++++++++++
b/xen/include/acpi/apei.h | 31 +
b/xen/include/xen/cper.h | 80 +++
xen/arch/x86/acpi/boot.c | 2
xen/drivers/acpi/Makefile | 1
xen/include/acpi/actbl1.h | 103 ++++
xen/include/asm-x86/fixmap.h | 3
xen/include/xen/acpi.h | 1
xen/include/xen/spinlock....
2016 Nov 18
3
[PATCH 1/3] virtio: Basic implementation of virtio pstore driver
...rmation,
On Wed, Nov 16, 2016 at 07:10:36AM -0500, Paolo Bonzini wrote:
> > Not sure how independent ERST is from ACPI and other specs. It looks
> > like referencing UEFI spec at least.
>
> It is just the format of error records that comes from the UEFI spec
> (include/linux/cper.h) but you can ignore it, I think. It should be
> handled by tools on the host side. For you, the error log address
> range contains a CPER header followed by a binary blob. In practice,
> you only need the record length field (bytes 20-23 of the header),
> though it may be a good id...
2016 Nov 18
3
[PATCH 1/3] virtio: Basic implementation of virtio pstore driver
...rmation,
On Wed, Nov 16, 2016 at 07:10:36AM -0500, Paolo Bonzini wrote:
> > Not sure how independent ERST is from ACPI and other specs. It looks
> > like referencing UEFI spec at least.
>
> It is just the format of error records that comes from the UEFI spec
> (include/linux/cper.h) but you can ignore it, I think. It should be
> handled by tools on the host side. For you, the error log address
> range contains a CPER header followed by a binary blob. In practice,
> you only need the record length field (bytes 20-23 of the header),
> though it may be a good id...