On Mon, 2014-09-08 at 10:23 -0700, Andy Lutomirski wrote:
> On Sep 8, 2014 8:18 AM, "Toshi Kani" wrote:
> >
> > On Sun, 2014-09-07 at 09:49 -0700, Andy Lutomirski wrote:
> > > On Sun, Sep 7, 2014 at 1:49 AM, Yigal Korman wrote:
> > > > I think that what confused Andy (or at least me) is the
On Sep 8, 2014 8:18 AM, "Toshi Kani" wrote:
>
> On Sun, 2014-09-07 at 09:49 -0700, Andy Lutomirski wrote:
> > On Sun, Sep 7, 2014 at 1:49 AM, Yigal Korman wrote:
> > > I think that what confused Andy (or at least me) is the documentation in
> > > Documentation/x86/pat.txt
> > > If it's
On Sun, 2014-09-07 at 09:49 -0700, Andy Lutomirski wrote:
> On Sun, Sep 7, 2014 at 1:49 AM, Yigal Korman wrote:
> > I think that what confused Andy (or at least me) is the documentation in
> > Documentation/x86/pat.txt
> > If it's possible, can you please update pat.txt as part of the patch?
>
On Sun, 2014-09-07 at 09:49 -0700, Andy Lutomirski wrote:
On Sun, Sep 7, 2014 at 1:49 AM, Yigal Korman yi...@plexistor.com wrote:
I think that what confused Andy (or at least me) is the documentation in
Documentation/x86/pat.txt
If it's possible, can you please update pat.txt as part of
On Sep 8, 2014 8:18 AM, Toshi Kani toshi.k...@hp.com wrote:
On Sun, 2014-09-07 at 09:49 -0700, Andy Lutomirski wrote:
On Sun, Sep 7, 2014 at 1:49 AM, Yigal Korman yi...@plexistor.com wrote:
I think that what confused Andy (or at least me) is the documentation in
On Mon, 2014-09-08 at 10:23 -0700, Andy Lutomirski wrote:
On Sep 8, 2014 8:18 AM, Toshi Kani toshi.k...@hp.com wrote:
On Sun, 2014-09-07 at 09:49 -0700, Andy Lutomirski wrote:
On Sun, Sep 7, 2014 at 1:49 AM, Yigal Korman yi...@plexistor.com wrote:
I think that what confused Andy (or at
On Sun, Sep 7, 2014 at 1:49 AM, Yigal Korman wrote:
> I think that what confused Andy (or at least me) is the documentation in
> Documentation/x86/pat.txt
> If it's possible, can you please update pat.txt as part of the patch?
Indeed. That file seems to indicate several times that the intended
I think that what confused Andy (or at least me) is the documentation in
Documentation/x86/pat.txt
If it's possible, can you please update pat.txt as part of the patch?
Thank you,
Yigal
On 04/09/2014 21:57, Toshi Kani wrote:
> On Thu, 2014-09-04 at 11:57 -0700, Andy Lutomirski wrote:
>> On Thu,
I think that what confused Andy (or at least me) is the documentation in
Documentation/x86/pat.txt
If it's possible, can you please update pat.txt as part of the patch?
Thank you,
Yigal
On 04/09/2014 21:57, Toshi Kani wrote:
On Thu, 2014-09-04 at 11:57 -0700, Andy Lutomirski wrote:
On Thu,
On Sun, Sep 7, 2014 at 1:49 AM, Yigal Korman yi...@plexistor.com wrote:
I think that what confused Andy (or at least me) is the documentation in
Documentation/x86/pat.txt
If it's possible, can you please update pat.txt as part of the patch?
Indeed. That file seems to indicate several times
On Thu, 2014-09-04 at 12:14 -0700, Andy Lutomirski wrote:
> On Thu, Sep 4, 2014 at 11:57 AM, Toshi Kani wrote:
> > On Thu, 2014-09-04 at 11:57 -0700, Andy Lutomirski wrote:
> >> On Thu, Sep 4, 2014 at 11:35 AM, Toshi Kani wrote:
> >> > This patch adds set_memory_wt(), set_memory_array_wt(), and
On Thu, Sep 4, 2014 at 11:57 AM, Toshi Kani wrote:
> On Thu, 2014-09-04 at 11:57 -0700, Andy Lutomirski wrote:
>> On Thu, Sep 4, 2014 at 11:35 AM, Toshi Kani wrote:
>> > This patch adds set_memory_wt(), set_memory_array_wt(), and
>> > set_pages_array_wt() for setting range(s) of memory to WT.
>>
On Thu, 2014-09-04 at 11:57 -0700, Andy Lutomirski wrote:
> On Thu, Sep 4, 2014 at 11:35 AM, Toshi Kani wrote:
> > This patch adds set_memory_wt(), set_memory_array_wt(), and
> > set_pages_array_wt() for setting range(s) of memory to WT.
> >
>
> Possibly dumb question: I thought that
On Thu, Sep 4, 2014 at 11:35 AM, Toshi Kani wrote:
> This patch adds set_memory_wt(), set_memory_array_wt(), and
> set_pages_array_wt() for setting range(s) of memory to WT.
>
Possibly dumb question: I thought that set_memory_xyz was only for
RAM. Is that incorrect?
--Andy
--
To unsubscribe
This patch adds set_memory_wt(), set_memory_array_wt(), and
set_pages_array_wt() for setting range(s) of memory to WT.
Note that reserve_memtype() only supports WT for non-RAM ranges
at this point.
Signed-off-by: Toshi Kani
---
arch/x86/include/asm/cacheflush.h |6 +++
This patch adds set_memory_wt(), set_memory_array_wt(), and
set_pages_array_wt() for setting range(s) of memory to WT.
Note that reserve_memtype() only supports WT for non-RAM ranges
at this point.
Signed-off-by: Toshi Kani toshi.k...@hp.com
---
arch/x86/include/asm/cacheflush.h |6 +++
On Thu, Sep 4, 2014 at 11:35 AM, Toshi Kani toshi.k...@hp.com wrote:
This patch adds set_memory_wt(), set_memory_array_wt(), and
set_pages_array_wt() for setting range(s) of memory to WT.
Possibly dumb question: I thought that set_memory_xyz was only for
RAM. Is that incorrect?
--Andy
--
To
On Thu, 2014-09-04 at 11:57 -0700, Andy Lutomirski wrote:
On Thu, Sep 4, 2014 at 11:35 AM, Toshi Kani toshi.k...@hp.com wrote:
This patch adds set_memory_wt(), set_memory_array_wt(), and
set_pages_array_wt() for setting range(s) of memory to WT.
Possibly dumb question: I thought that
On Thu, Sep 4, 2014 at 11:57 AM, Toshi Kani toshi.k...@hp.com wrote:
On Thu, 2014-09-04 at 11:57 -0700, Andy Lutomirski wrote:
On Thu, Sep 4, 2014 at 11:35 AM, Toshi Kani toshi.k...@hp.com wrote:
This patch adds set_memory_wt(), set_memory_array_wt(), and
set_pages_array_wt() for setting
On Thu, 2014-09-04 at 12:14 -0700, Andy Lutomirski wrote:
On Thu, Sep 4, 2014 at 11:57 AM, Toshi Kani toshi.k...@hp.com wrote:
On Thu, 2014-09-04 at 11:57 -0700, Andy Lutomirski wrote:
On Thu, Sep 4, 2014 at 11:35 AM, Toshi Kani toshi.k...@hp.com wrote:
This patch adds set_memory_wt(),
20 matches
Mail list logo
