All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 24/28] ia64/xen: time paravirtualization
Date: Thu, 21 Feb 2008 23:11:04 +0000	[thread overview]
Message-ID: <47BE0508.7080203@goop.org> (raw)

yamahata@valinux.co.jp wrote:
> diff --git a/arch/ia64/kernel/time.c b/arch/ia64/kernel/time.c
> index 17fda52..1bb0362 100644
> --- a/arch/ia64/kernel/time.c
> +++ b/arch/ia64/kernel/time.c
> @@ -29,6 +29,14 @@
>  #include <asm/sections.h>
>  #include <asm/system.h>
>  
> +#include <asm/xen/hypervisor.h>
> +#ifdef CONFIG_XEN
> +#include <linux/kernel_stat.h>
> +#include <linux/posix-timers.h>
> +#include <xen/interface/vcpu.h>
> +#include <asm/percpu.h>
> +#endif
> +

ia64 doesn't use clocksources yet?  Couldn't you share a lot of this 
with the 32-bit Xen time code (esp stolen time accounting)?

    J

         reply	other threads:[~2008-02-21 23:11 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080221091731.641745000@ls.local.valinux.co.jp>
2008-02-21  9:17 ` [PATCH 01/28] ia64/xen: introduce ia64_set_rr0_to_rr4() to make kernel paravirtualization friendly yamahata
2008-02-21  9:17 ` [PATCH 02/28] ia64/xen: introduce ia64_get_psr_i() " yamahata
2008-02-21  9:17 ` [PATCH 03/28] ia64/xen: increase IA64_MAX_RSVD_REGIONS yamahata
2008-02-21  9:17 ` [PATCH 04/28] ia64/xen: introduce synch bitops which is necessary for ia64/xen support yamahata
2008-02-21  9:17 ` [PATCH 05/28] ia64/xen: import xen hypercall header file yamahata
2008-02-21  9:17 ` [PATCH 06/28] ia64/xen: define xen assembler constants which will be used later yamahata
2008-02-21  9:17 ` [PATCH 07/28] ia64/xen: detect xen environment at early boot time and do minimal initialization yamahata
2008-02-21  9:17 ` [PATCH 08/28] RFC: ia64/xen: xen hand written assembly code paravirtualization yamahata
2008-02-21  9:17 ` [PATCH 09/28] ia64/xen: paravirtualize pal_call_static() yamahata
2008-02-21  9:17 ` [PATCH 10/28] RFC: ia64/xen: introduce xen paravirtualized intrinsic operations for privileged instruction yamahata
2008-02-21  9:17 ` [PATCH 11/28] ia64: introduce basic facilities for binary patching yamahata
2008-02-21  9:17 ` [PATCH 12/28] RFC: ia64/xen: xen privileged instruction intrinsics " yamahata
2008-02-21  9:17 ` [PATCH 13/28] ia64/xen: introduce xen hypercall routines necessary for domU yamahata
2008-02-21  9:17 ` [PATCH 14/28] ia64/xen: ia64 domU part of xencomm yamahata
2008-02-21  9:17 ` [PATCH 15/28] ia64/xen: define xen_alloc_vm_area()/xen_free_vm_area() for ia64 arch yamahata
2008-02-21  9:17 ` [PATCH 16/28] ia64/xen: basic helper routines for xen/ia64 yamahata
2008-02-21  9:17 ` [PATCH 17/28] ia64/xen: domU initialization code yamahata
2008-02-21  9:17 ` [PATCH 18/28] ia64/xen: iosapic paravirtualization yamahata
2008-02-21  9:17 ` [PATCH 19/28] ia64/xen: xen domU irq chip introducing some helper functions, xen_send_ipi yamahata
2008-02-21  9:17 ` [PATCH 20/28] ia64/xen: domU xen machine vector without dma api yamahata
2008-02-21  9:17 ` [PATCH 21/28] ia64/xen: define xen related address conversion helper functions for domU yamahata
2008-02-21  9:17 ` [PATCH 22/28] ia64/xen: mca paravirtualization yamahata
2008-02-21  9:17 ` [PATCH 23/28] ia64/xen: sal paravirtualization yamahata
2008-02-21  9:17 ` [PATCH 24/28] ia64/xen: time paravirtualization yamahata
2008-02-21  9:17 ` [PATCH 25/28] ia64/xen: gate page paravirtualization yamahata
2008-02-21  9:17 ` [PATCH 26/28] ia64/xen: fsys paravirtualization yamahata
2008-02-21  9:17 ` [PATCH 27/28] ia64/xen: update Kconfig to allow xen domU Linux yamahata
2008-02-21  9:17 ` [PATCH 28/28] ia64/xen: add ia64/xen domU config yamahata
     [not found] ` <20080221091904.811793000@ls.local.valinux.co.jp>
2008-02-21 23:08   ` [PATCH 20/28] ia64/xen: domU xen machine vector without dma api Jeremy Fitzhardinge
     [not found] ` <20080221091906.007909000@ls.local.valinux.co.jp>
2008-02-21 23:11   ` Jeremy Fitzhardinge [this message]
2008-02-22  3:57     ` [PATCH 24/28] ia64/xen: time paravirtualization Isaku Yamahata
2008-02-22  3:57     ` Isaku Yamahata
2008-02-22  5:10     ` Isaku Yamahata
2008-02-21 23:11   ` Jeremy Fitzhardinge
     [not found] ` <20080221091904.517166000@ls.local.valinux.co.jp>
2008-02-21 23:22   ` [PATCH 19/28] ia64/xen: xen domU irq chip introducing some helper functions, xen_send_ipi Jeremy Fitzhardinge
     [not found] ` <20080221091905.122606000@ls.local.valinux.co.jp>
2008-02-21 23:45   ` [PATCH 21/28] ia64/xen: define xen related address conversion helper functions for domU Jeremy Fitzhardinge
     [not found] ` <20080221091902.716789000@ls.local.valinux.co.jp>
2008-02-21 23:47   ` [PATCH 13/28] ia64/xen: introduce xen hypercall routines necessary " Jeremy Fitzhardinge
2008-02-21 23:47   ` [PATCH 13/28] ia64/xen: introduce xen hypercall routines necessary Jeremy Fitzhardinge
2008-02-22  3:54     ` [PATCH 13/28] ia64/xen: introduce xen hypercall routines necessary for domU Isaku Yamahata
2008-02-25 18:36       ` [kvm-ia64-devel] [PATCH 13/28] ia64/xen: introduce xenhypercall " Dong, Eddie
2008-02-25 18:36       ` Dong, Eddie
2008-02-26  1:44         ` Isaku Yamahata
2008-02-26  1:44         ` Isaku Yamahata
2008-02-22  3:54     ` [PATCH 13/28] ia64/xen: introduce xen hypercall " Isaku Yamahata
2008-02-22  5:10     ` 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=47BE0508.7080203@goop.org \
    --to=jeremy@goop.org \
    --cc=linux-ia64@vger.kernel.org \
    /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.