From: Nick Piggin <npiggin@suse.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"elendil@planet.nl" <elendil@planet.nl>,
"thellstrom@vmware.com" <thellstrom@vmware.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@elte.hu" <mingo@elte.hu>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:x86/urgent] VM, x86, PAT: Change is_linear_pfn_mapping to not use vm_pgoff
Date: Sat, 14 Mar 2009 03:52:38 +0100 [thread overview]
Message-ID: <20090314025238.GA32065@wotan.suse.de> (raw)
In-Reply-To: <1236963607.4529.111.camel@localhost.localdomain>
On Fri, Mar 13, 2009 at 10:00:07AM -0700, Pallipadi, Venkatesh wrote:
> On Fri, 2009-03-13 at 09:25 -0700, Nick Piggin wrote:
> > Why not just use another vm_flag for 2.6.29 and earlier (we have 2 left),
> > then do some flag rationalisation in 2.6.30?
> >
> > But I do like just avoiding these games entirely and encoding it
> > explicitly.
> >
>
> Totally agree that this is ugly. But, I didn't like taking away one bit
> for such a light usage. VM_INSERTPAGE is hardly ever used in the kernel
> (wherever it is used, it is checked along with VM_PFNMAP).
That is a concern, but I think it makes the patch more intrusive
than a simple fix that might possibly introduce a bug. So for 2.6.29
we have spare flags so can use one of those for the fix.
> OK. I will resend the patch with taking away one of the available bits.
> But, I feel we need to do some multiplexing here, in a clean manner, for
> future.
That would always be appreciated. There are probably several flags that
can go away (eg. VM_RESERVED, VM_INSERTPAGE), others that can be merged
(eg nommu flags with mmu flags), others that can be one scalar value
rather than several binary values etc.
Also, if worst comes to worst, I think we could probably make vm_flags
64-bit on 32-bit compiles to get another 32 bits. Of course I'd rather
not until no other options left for reducing flags ;)
next prev parent reply other threads:[~2009-03-14 2:52 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
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 [this message]
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=20090314025238.GA32065@wotan.suse.de \
--to=npiggin@suse.de \
--cc=ebiederm@xmission.com \
--cc=elendil@planet.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome