From: Nick Piggin <npiggin@suse.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
H Peter Anvin <hpa@zytor.com>, Hugh Dickins <hugh@veritas.com>,
Roland Dreier <rdreier@cisco.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Arjan van de Ven <arjan@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>
Subject: Re: [patch 2/8] x86 PAT: set VM_PFNMAP flag in vm_insert_pfn
Date: Fri, 21 Nov 2008 01:50:26 +0100 [thread overview]
Message-ID: <20081121005026.GB27293@wotan.suse.de> (raw)
In-Reply-To: <7E82351C108FA840AB1866AC776AEC4642A9C879@orsmsx505.amr.corp.intel.com>
On Thu, Nov 20, 2008 at 03:42:32PM -0800, Pallipadi, Venkatesh wrote:
>
>
> >-----Original Message-----
> >From: linux-kernel-owner@vger.kernel.org
> >[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Ingo Molnar
> >Sent: Tuesday, November 18, 2008 1:38 PM
> >To: Nick Piggin
> >Cc: Pallipadi, Venkatesh; Thomas Gleixner; H Peter Anvin; Hugh
> >Dickins; Roland Dreier; Jesse Barnes; Jeremy Fitzhardinge;
> >Arjan van de Ven; linux-kernel@vger.kernel.org; Siddha, Suresh B
> >Subject: Re: [patch 2/8] x86 PAT: set VM_PFNMAP flag in vm_insert_pfn
> >
> >
> >patchset need acks from MM folks - Andrew, Nick or Hugh - we cannot
> >just queue them up in the x86/pat tree without agreement from MM
> >maintainers.
> >
>
> OK. Feedback based on the discussions on this patchset, this particular patch
> set VM_PFNMAP flag in vm_insert_pfn
> is not really needed and we should rather BUG_ON on that not being set.
> And there were few more comments on one other generic vm patch from Nick.
>
> I will resend the entire patchset with changes soon and then we can work
> out the logistics.
So long as it has been reviewed by mm people (cc'ing linux-mm might be
nice), I don't care so much how it makes its way upstream. If it was
a lot of code, it might make sense to slowly work dependencies though
various subsystems... but this isn't too much on the mm side, and it is
primarily support code for x86 subsystem feature so I don't mind myself
if it went via the x86 tree, with appropriate acks.
next prev parent reply other threads:[~2008-11-21 0:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 21:26 [patch 0/8] x86 PAT: track pfnmap mappings with remap_pfn_range and vm_insert_pfn Venkatesh Pallipadi
2008-11-12 21:26 ` [patch 1/8] x86 PAT: store vm_pgoff for all linear_over_vma_region mappings Venkatesh Pallipadi
2008-11-12 21:26 ` [patch 2/8] x86 PAT: set VM_PFNMAP flag in vm_insert_pfn Venkatesh Pallipadi
2008-11-12 23:23 ` Nick Piggin
2008-11-13 0:02 ` Pallipadi, Venkatesh
2008-11-13 3:44 ` Nick Piggin
2008-11-13 18:47 ` Pallipadi, Venkatesh
2008-11-14 2:05 ` Nick Piggin
2008-11-14 21:35 ` Pallipadi, Venkatesh
2008-11-17 2:30 ` Nick Piggin
2008-11-18 21:37 ` Ingo Molnar
2008-11-20 23:42 ` Pallipadi, Venkatesh
2008-11-21 0:50 ` Nick Piggin [this message]
2008-11-15 7:38 ` Benjamin Herrenschmidt
2008-11-12 21:26 ` [patch 3/8] x86 PAT: Add follow_pfnmp_pte routine to help tracking pfnmap pages Venkatesh Pallipadi
2008-11-12 23:27 ` Nick Piggin
2008-11-12 23:54 ` Pallipadi, Venkatesh
2008-11-12 21:26 ` [patch 4/8] x86 PAT: hooks in generic vm code to help archs to track pfnmap regions Venkatesh Pallipadi
2008-12-16 19:57 ` Andrew Morton
2008-12-16 20:07 ` Pallipadi, Venkatesh
2008-12-16 20:13 ` Andrew Morton
2008-11-12 21:26 ` [patch 5/8] x86 PAT: Implement track/untrack of pfnmap regions for x86 Venkatesh Pallipadi
2008-12-16 20:07 ` Andrew Morton
2008-12-16 23:19 ` Pallipadi, Venkatesh
2008-11-12 21:26 ` [patch 6/8] x86 PAT: change pgprot_noncached to uc_minus instead of strong uc Venkatesh Pallipadi
2008-11-12 21:26 ` [patch 7/8] x86 PAT: add pgprot_writecombine() interface for drivers Venkatesh Pallipadi
2008-11-12 21:26 ` [patch 8/8] x86 PAT: update documentation to cover pgprot and remap_pfn related changes Venkatesh Pallipadi
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=20081121005026.GB27293@wotan.suse.de \
--to=npiggin@suse.de \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=hugh@veritas.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rdreier@cisco.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--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.