From: Ingo Molnar <mingo@elte.hu>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Nick Piggin <npiggin@suse.de>
Subject: Re: 2.6.29 pat issue
Date: Wed, 11 Mar 2009 10:33:38 +0100 [thread overview]
Message-ID: <20090311093338.GC12814@elte.hu> (raw)
In-Reply-To: <49B781B6.3060704@vmware.com>
* Thomas Hellstrom <thellstrom@vmware.com> wrote:
> Pallipadi, Venkatesh wrote:
>> On Tue, 2009-03-10 at 01:22 -0700, Thomas Hellstrom wrote:
>>
>>> Pallipadi, Venkatesh wrote:
>>>
>>>> On Fri, Mar 06, 2009 at 03:44:07PM -0800, Thomas Hellstrom wrote:
>>>>
>>>>> We get the warning when we insert RAM pages using vm_insert_pfn().
>>>>> Having normal RAM pages backing a PFN papping is a valid thing.
>>>>>
>>>>>
>>>> OK. Below is the updated patch that should fix this fully. Can you confirm?
>>>>
>>>> Thanks,
>>>> Venki
>>>>
>>>>
>>> Yes, this patch should fix the problem. I'm still concerned about the
>>> overhead of going through the
>>> RAM test for each inserted page.
>>>
>>> Why can't a pfn_valid() test be used in vm_insert_pfn()?
>>>
>>>
>>
>> Because we may have to track the RAM pages as well in future. We are
>> changing the e820 RAM check and making it use pfn_valid. But, for that
>> we have to change more things in tracking of RAM pages. Today we use one
>> bit in page struct without any refcounting. But, more changes there are
>> on ts way. This change here should keep the current kernel fine without
>> any regression.
>>
>> Thanks,
>> Venki
>>
>>
> Ok, I understand.
> and yes, the regression should be fixed with the patch.
Good. Venki, mind resending the patch against tip:master, with a
proper subject line, changelog and Acked-by in place? Thanks,
Ingo
next prev parent reply other threads:[~2009-03-11 9:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 12:47 2.6.29 pat issue Thomas Hellström
2009-02-05 18:03 ` Pallipadi, Venkatesh
2009-02-05 21:32 ` Thomas Hellstrom
2009-02-05 23:08 ` Pallipadi, Venkatesh
2009-02-06 9:51 ` Thomas Hellström
2009-02-06 1:11 ` Eric W. Biederman
2009-02-06 9:43 ` Thomas Hellström
2009-03-04 6:08 ` Pallipadi, Venkatesh
2009-03-04 9:56 ` Thomas Hellstrom
2009-03-06 22:38 ` Pallipadi, Venkatesh
2009-03-06 23:44 ` Thomas Hellstrom
2009-03-10 1:39 ` Pallipadi, Venkatesh
2009-03-10 8:22 ` Thomas Hellstrom
2009-03-10 17:42 ` Pallipadi, Venkatesh
2009-03-11 9:17 ` Thomas Hellstrom
2009-03-11 9:33 ` Ingo Molnar [this message]
2009-03-11 17:54 ` [PATCH] VM, x86, PAT: Change implementation of is_linear_pfn_mapping Pallipadi, Venkatesh
2009-03-11 22:09 ` Frans Pop
2009-03-12 0:31 ` Pallipadi, Venkatesh
2009-03-12 3:22 ` Pallipadi, Venkatesh
2009-03-12 5:45 ` Frans Pop
2009-03-12 18:59 ` Pallipadi, Venkatesh
2009-03-12 20:30 ` Frans Pop
2009-03-12 22:48 ` Pallipadi, Venkatesh
2009-03-13 0:36 ` Ingo Molnar
2009-03-13 0:45 ` [PATCH] VM, x86, PAT: Change is_linear_pfn_mapping to not use vm_pgoff Pallipadi, Venkatesh
2009-03-13 4:03 ` [tip:x86/urgent] " Pallipadi, Venkatesh
2009-03-13 16:25 ` Nick Piggin
2009-03-13 17:00 ` Pallipadi, Venkatesh
2009-03-14 2:52 ` Nick Piggin
2009-03-13 23:35 ` [PATCH] Add a new vm flag to track full pfnmap at mmap Pallipadi, Venkatesh
2009-03-14 2:53 ` Nick Piggin
2009-03-14 8:54 ` [tip:x86/urgent] VM, x86, PAT: add " Pallipadi, Venkatesh
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=20090311093338.GC12814@elte.hu \
--to=mingo@elte.hu \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=suresh.b.siddha@intel.com \
--cc=thellstrom@vmware.com \
--cc=venkatesh.pallipadi@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.