On 1/25/2019 11:15 AM, Dan Williams wrote:
On Fri, Jan 25, 2019 at 11:10 AM Jane Chu wrote:
On 1/25/2019 10:20 AM, Verma, Vishal L wrote:
On Fri, 2019-01-25 at 09:18 -0800, Dan Williams wrote:
On Fri, Jan 25, 2019 at 12:20 AM Du, Fan wrote:
Dan
Thanks for the insights!
Can I say, th
Add bash completion helpers to contrib/ndctl to also allow for daxctl
completion. This makes it so we have a single bash-completion script
that is installed, and it provides completions for both ndctl and
daxctl. As a bonus, some of the common functions can also get reused by
both.
Cc: Dan William
On 1/25/19 1:18 PM, Bjorn Helgaas wrote:
> On Thu, Jan 24, 2019 at 5:21 PM Dave Hansen
> wrote:
>> diff -puN kernel/resource.c~move-request_region-check kernel/resource.c
>> --- a/kernel/resource.c~move-request_region-check 2019-01-24
>> 15:13:14.453199539 -0800
>> +++ b/kernel/resource.c
On Fri, Jan 25, 2019 at 3:10 PM Dave Hansen wrote:
>
> On 1/25/19 1:02 PM, Bjorn Helgaas wrote:
> >> @@ -453,7 +453,7 @@ int walk_system_ram_range(unsigned long
> >> unsigned long flags;
> >> struct resource res;
> >> unsigned long pfn, end_pfn;
> >> - int ret = -1;
>
On Thu, Jan 24, 2019 at 5:21 PM Dave Hansen wrote:
>
>
> From: Dave Hansen
>
> HMM consumes physical address space for its own use, even
> though nothing is mapped or accessible there. It uses a
> special resource description (IORES_DESC_DEVICE_PRIVATE_MEMORY)
> to uniquely identify these areas.
On 1/25/19 1:02 PM, Bjorn Helgaas wrote:
>> @@ -453,7 +453,7 @@ int walk_system_ram_range(unsigned long
>> unsigned long flags;
>> struct resource res;
>> unsigned long pfn, end_pfn;
>> - int ret = -1;
>> + int ret = -EINVAL;
> Can you either make a similar chang
On Thu, Jan 24, 2019 at 5:21 PM Dave Hansen wrote:
>
>
> From: Dave Hansen
>
> walk_system_ram_range() can return an error code either becuase *it*
> failed, or because the 'func' that it calls returned an error. The
> memory hotplug does the following:
>
> ret = walk_system_ram_range(..
On Fri, Jan 25, 2019 at 11:10 AM Jane Chu wrote:
>
>
> On 1/25/2019 10:20 AM, Verma, Vishal L wrote:
> >
> > On Fri, 2019-01-25 at 09:18 -0800, Dan Williams wrote:
> >> On Fri, Jan 25, 2019 at 12:20 AM Du, Fan wrote:
> >>> Dan
> >>>
> >>> Thanks for the insights!
> >>>
> >>> Can I say, the UCE is
On 1/25/2019 10:20 AM, Verma, Vishal L wrote:
On Fri, 2019-01-25 at 09:18 -0800, Dan Williams wrote:
On Fri, Jan 25, 2019 at 12:20 AM Du, Fan wrote:
Dan
Thanks for the insights!
Can I say, the UCE is delivered from h/w to OS in a single way in
case of machine
check, only PMEM/DAX stuff fi
On Thu, Jan 24, 2019 at 03:14:41PM -0800, Dave Hansen wrote:
> v3 spurred a bunch of really good discussion. Thanks to everybody
> that made comments and suggestions!
>
> I would still love some Acks on this from the folks on cc, even if it
> is on just the patch touching your area.
>
> Note: th
On Thu, Jan 24, 2019 at 03:14:44PM -0800, Dave Hansen wrote:
>
> From: Dave Hansen
>
> HMM consumes physical address space for its own use, even
> though nothing is mapped or accessible there. It uses a
> special resource description (IORES_DESC_DEVICE_PRIVATE_MEMORY)
> to uniquely identify the
On Fri, 2019-01-25 at 09:18 -0800, Dan Williams wrote:
> On Fri, Jan 25, 2019 at 12:20 AM Du, Fan wrote:
> > Dan
> >
> > Thanks for the insights!
> >
> > Can I say, the UCE is delivered from h/w to OS in a single way in
> > case of machine
> > check, only PMEM/DAX stuff filter out UC address a
On Fri, Jan 25, 2019 at 12:20 AM Du, Fan wrote:
>
> Dan
>
> Thanks for the insights!
>
> Can I say, the UCE is delivered from h/w to OS in a single way in case of
> machine
> check, only PMEM/DAX stuff filter out UC address and managed in its own way by
> badblocks, if PMEM/DAX doesn't do so, the
Your email client cannot read this email. To view it online, please go here:
http://track.yoganews.info/campaigns/webversion/Nzk1Nw==/MzQ0NTA0OA==/MjU5 Have we gotten to the wrong address? If so, we apologize and you can easily
press the Unsubscribe me from this listDear colleagues, Following ou
Dan
Thanks for the insights!
Can I say, the UCE is delivered from h/w to OS in a single way in case of
machine
check, only PMEM/DAX stuff filter out UC address and managed in its own way by
badblocks, if PMEM/DAX doesn't do so, then common RAS workflow will kick in,
right?
And how about when AR
15 matches
Mail list logo
