mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: remove end_pfn in 64bit
Date: Thu, 26 Jun 2008 12:04:57 +0200	[thread overview]
Message-ID: <20080626100457.GC19573@elte.hu> (raw)
In-Reply-To: <4862B915.3010001@goop.org>


* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> Ingo Molnar wrote:
>> * Yinghai Lu <yhlu.kernel@gmail.com> wrote:
>>
>>   
>>> and use max_pfn directly.
>>>
>>> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
>>>     
>>
>> applied to tip/x86/setup-memory - thanks Yinghai. I have picked up 
>> these patches:
>>
>> Ingo Molnar (1):
>>       Merge branch 'x86/setup-memory'
>>
>> Yinghai Lu (6):
>>       x86: fix e820_update_range size when overlapping
>>       x86: get max_pfn_mapped in init_memory_mapping
>>       x86: add table_top check for alloc_low_page in 64 bit
>>       x86: change size if e820_update/remove_range
>>       x86: numa 32 using apicid_2_node to get node for logical_apicid
>>       x86: remove end_pfn in 64bit
>>   
>
> Did you CC: this to me to indicate that "x86_64: replace end_pfn with 
> num_physpages" conflicts massively with this patch?  Fortunately I 
> don't depend on it, so I don't mind much.

yeah, wanted to notify you, in case you were wondering about interaction 
in this area :)

	Ingo

      parent reply	other threads:[~2008-06-26 10:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25  5:13 [PATCH] x86: numa 32 using apicid_2_node to get node for logical_apicid Yinghai Lu
2008-06-25  5:14 ` [PATCH] x86: remove end_pfn in 64bit Yinghai Lu
2008-06-25  8:14   ` [PATCH] x86: Merge setup_32/64.c into setup.c Yinghai Lu
2008-06-25 15:36     ` Ingo Molnar
2008-06-25 15:44       ` Yinghai Lu
2008-06-25 16:43         ` Ingo Molnar
2008-06-25 17:28           ` Yinghai Lu
2008-06-25 17:38             ` Mike Travis
2008-06-25 17:46               ` Yinghai Lu
2008-06-25 17:48                 ` H. Peter Anvin
2008-06-25 15:41   ` [PATCH] x86: remove end_pfn in 64bit Ingo Molnar
2008-06-25 21:31     ` Jeremy Fitzhardinge
2008-06-25 21:57       ` Yinghai Lu
2008-06-25 22:21         ` Jeremy Fitzhardinge
2008-06-25 23:14           ` Yinghai Lu
2008-06-25 23:16             ` Jeremy Fitzhardinge
2008-06-26 10:04       ` Ingo Molnar [this message]

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=20080626100457.GC19573@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@gmail.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