All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] fix ia64 breakage with PHYSDEVOP_pirq_eoi_mfn (was Re: [PATCH 2/2] linux/x86: use shared page indicating the need for an EOI notification)
Date: Wed, 10 Dec 2008 07:59:14 +0000	[thread overview]
Message-ID: <493F84E2.76E4.0078.0@novell.com> (raw)
In-Reply-To: <20081210040936.GE15447%yamahata@valinux.co.jp>

>>> Isaku Yamahata <yamahata@valinux.co.jp> 10.12.08 05:09 >>>
>Like this?

Almost.

>--- a/include/asm-i386/mach-xen/asm/pgtable.h
>+++ b/include/asm-i386/mach-xen/asm/pgtable.h
>@@ -488,6 +488,17 @@ void make_pages_writable(void *va, unsig
> 	(((maddr_t)pte_mfn(*virt_to_ptep(va)) << PAGE_SHIFT)		\
> 	 | ((unsigned long)(va) & (PAGE_SIZE - 1)))
> 
>+#ifdef CONFIG_HIGHPTE
>+#define ptep_to_machine(ptep)						\
>+({									\
>+	(unsigned long)(ptep) >= (unsigned long)high_memory?		\
>+		arbitrary_virt_to_machine(ptep) :			\
>+		virt_to_machine(ptep);					\
>+})

I was intending to make use of kmap_atomic_to_page() here. Due to the
check at the beginning of that function, it would even be possible to get
away without a conditional in the highpte case of the macro:

#define ptep_to_machine(ptep) page_to_phys(kmap_atomic_to_page(ptep))

page_to_phys() and page_to_bus() could be used here interchangeably due
to them being identical on x86.

Jan

  reply	other threads:[~2008-12-10  7:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 13:36 [PATCH] fix ia64 breakage with PHYSDEVOP_pirq_eoi_mfn (was Re: [PATCH 2/2] linux/x86: use shared page indicating the need for an EOI notification) Jan Beulich
2008-12-09  3:40 ` Isaku Yamahata
2008-12-09 10:04   ` Jan Beulich
2008-12-09 10:43     ` Isaku Yamahata
2008-12-09 10:54       ` Jan Beulich
2008-12-09 11:06         ` Keir Fraser
2008-12-10  4:08           ` Isaku Yamahata
2008-12-10  4:16             ` Isaku Yamahata
2008-12-10  9:21               ` [PATCH] fix ia64 breakage with PHYSDEVOP_pirq_eoi_mfn (was Re:[PATCH 2/2] linux/x86: use shared page indicatingthe " Jan Beulich
2008-12-10 10:07                 ` Keir Fraser
2008-12-10 10:23                   ` [PATCH] fix ia64 breakage with PHYSDEVOP_pirq_eoi_mfn (wasRe:[PATCH 2/2] linux/x86: use shared page indicatingthe need foran " Jan Beulich
2008-12-10  4:09         ` [PATCH] fix ia64 breakage with PHYSDEVOP_pirq_eoi_mfn (was Re: [PATCH 2/2] linux/x86: use shared page indicating the need for an " Isaku Yamahata
2008-12-10  7:59           ` Jan Beulich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-28  9:59 [PATCH 2/2] linux/x86: use shared page indicating the need for an EOI notification Jan Beulich
2008-12-03  2:07 ` [PATCH] fix ia64 breakage with PHYSDEVOP_pirq_eoi_mfn (was Re: [PATCH 2/2] linux/x86: use shared page indicating the need for an EOI notification) Isaku Yamahata
2008-12-03  7:58   ` Jan Beulich
2008-12-03  8:44     ` Isaku Yamahata
2008-12-03  8:58       ` Jan Beulich
2008-12-03  9:20         ` Isaku Yamahata
2008-12-03  9:31           ` Jan Beulich
2008-12-03  9:59             ` Isaku Yamahata
2008-12-03 10:08               ` Keir Fraser
2008-12-03 10:13                 ` Isaku Yamahata
2008-12-03 10:15                   ` Keir Fraser
2008-12-03 10:23                     ` Isaku Yamahata

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=493F84E2.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yamahata@valinux.co.jp \
    /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.