LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Glauber de Oliveira Costa <gcosta@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Marcelo Tosatti <marcelo@kvack.org>,
ehabkost@redhat.com, glommer@gmail.com, jeremy@goop.org,
chrisw@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fill in missing pv_mmu_ops entries for PAGETABLE_LEVELS >= 3
Date: Tue, 29 Jan 2008 09:33:25 +1100 [thread overview]
Message-ID: <479E5835.7000803@redhat.com> (raw)
In-Reply-To: <20080122123029.GD31253@elte.hu>
Ingo Molnar wrote:
> * Marcelo Tosatti <marcelo@kvack.org> wrote:
>
>
>>> The first fix is not even specific for PARAVIRT, and it's actually
>>> preventing the whole tree from booting.
>>>
>>>
>> And the following allows PARAVIRT kernels to boot on x86_64.
>>
>
>
>> Fill in missing pagetable manipulation entries in pv_mmu_ops
>> for PAGETABLE_LEVELS >= 3.
>>
>
> thanks Marcelo - picked this up and the other changes as well. I guess
> the only thing missing at the moment is the proper Kconfig changes to
> allow the building of a 64-bit PARAVIRT kernel?
> Ingo
>
For normal hardware yes. But I still have a vsmp patch in the queue.
prev parent reply other threads:[~2008-01-28 22:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 17:20 [PATCH 0/10] Tree fixes for PARAVIRT Glauber de Oliveira Costa
2008-01-18 17:20 ` [PATCH 1/10] add missing parameter for lookup_address Glauber de Oliveira Costa
2008-01-18 17:20 ` [PATCH 2/10] add stringify header Glauber de Oliveira Costa
2008-01-18 17:20 ` [PATCH 3/10] provide a native_init_IRQ function to x86_64 Glauber de Oliveira Costa
2008-01-18 17:20 ` [PATCH 4/10] put generic mm_hooks include into PARAVIRT Glauber de Oliveira Costa
2008-01-18 17:20 ` [PATCH 5/10] puts read and write cr8 into pv_cpu_ops Glauber de Oliveira Costa
2008-01-18 17:20 ` [PATCH 6/10] provide read and write cr8 paravirt hooks Glauber de Oliveira Costa
2008-01-18 17:20 ` [PATCH 7/10] fill pv_cpu_ops structure with cr8 fields Glauber de Oliveira Costa
2008-01-18 17:20 ` [PATCH 8/10] add asm_offset PARAVIRT constants Glauber de Oliveira Costa
2008-01-18 17:20 ` [PATCH 9/10] provide __parainstructions section Glauber de Oliveira Costa
2008-01-18 17:20 ` [PATCH 10/10] change function orders in paravirt.h Glauber de Oliveira Costa
2008-01-18 20:24 ` Jeremy Fitzhardinge
2008-01-18 20:41 ` [PATCH 9/10] provide __parainstructions section Sam Ravnborg
2008-01-18 22:47 ` Jeremy Fitzhardinge
2008-01-18 20:26 ` [PATCH 1/10] add missing parameter for lookup_address Chris Wright
2008-01-19 1:16 ` Andi Kleen
2008-01-18 20:32 ` [PATCH 0/10] Tree fixes for PARAVIRT Ingo Molnar
2008-01-18 21:37 ` Ingo Molnar
2008-01-18 21:54 ` Zachary Amsden
2008-01-18 22:02 ` Ingo Molnar
2008-01-19 1:24 ` Glauber de Oliveira Costa
2008-01-22 12:20 ` Ingo Molnar
2008-01-18 22:31 ` Jeremy Fitzhardinge
2008-01-19 18:19 ` [PATCH] fill in missing pv_mmu_ops entries for PAGETABLE_LEVELS >= 3 Marcelo Tosatti
2008-01-20 5:05 ` Jeremy Fitzhardinge
2008-01-21 20:44 ` Eduardo Pereira Habkost
2008-01-21 21:19 ` Jeremy Fitzhardinge
2008-01-22 12:30 ` Ingo Molnar
2008-01-28 22:33 ` Glauber de Oliveira Costa [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=479E5835.7000803@redhat.com \
--to=gcosta@redhat.com \
--cc=chrisw@redhat.com \
--cc=ehabkost@redhat.com \
--cc=glommer@gmail.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).