public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: Glauber de Oliveira Costa <gcosta@redhat.com>,
	linux-kernel@vger.kernel.org
Cc: jeremy@goop.org, hollisb@us.ibm.com,
	kvm-devel@lists.sourceforge.net, avi@qumranet.com
Subject: Re: [kvm-devel] include files for kvmclock
Date: Wed, 07 Nov 2007 17:16:37 +0900	[thread overview]
Message-ID: <1DC8211684B62Btakebe_akio@jp.fujitsu.com> (raw)
In-Reply-To: <11943875433821-git-send-email-gcosta@redhat.com>

Hi, Glauber

This is interesting facility. :-)

>+#define KVM_HCALL_REGISTER_CLOCK	1
>+
>+union kvm_hv_clock {
>+	struct {
>+		u64 tsc_mult;
>+		u64 now_ns;
>+		/* That's the wall clock, not the water closet */
>+		u64 wc_sec;
>+		u64 wc_nsec;
>+		u64 last_tsc;
>+		/* At first, we could use the tsc value as a marker, but Jeremy
>+		 * well noted that it will cause us locking problems in 32-bit
>+		 * sys, so we have a special version field */
>+		u32 version;
>+	};
>+	char page_align[PAGE_SIZE];
>+};
>+
Why does kvm_hv_clock need page_align?
And also the kvm_hv_clock is alloced with kvm_vcpu,
so the align is not enough, isn't it?
I thik __atribute__((__aligne__(PAGE_SIZE)))) is better than it.

Best Regards,

Akio Takebe


  parent reply	other threads:[~2007-11-07  8:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06 22:18 KVM paravirt clocksource - Take 3 out of <put your number here> Glauber de Oliveira Costa
2007-11-06 22:18 ` include files for kvmclock Glauber de Oliveira Costa
2007-11-06 21:35   ` [kvm-devel] " Glauber de Oliveira Costa
2007-11-07  5:55     ` Avi Kivity
2007-11-07  5:58       ` Jeremy Fitzhardinge
2007-11-07 12:49         ` Glauber de Oliveira Costa
2007-11-06 22:18   ` kvmclock - the host part Glauber de Oliveira Costa
2007-11-06 22:18     ` kvmclock implementation, the guest part Glauber de Oliveira Costa
2007-11-07  5:50     ` kvmclock - the host part Avi Kivity
2007-11-07 13:08       ` Glauber de Oliveira Costa
2007-11-07 13:59         ` Avi Kivity
2007-11-06 22:50   ` include files for kvmclock Jeremy Fitzhardinge
2007-11-06 22:58     ` Glauber de Oliveira Costa
2007-11-07  8:16   ` Akio Takebe [this message]
2007-11-07 13:16     ` [kvm-devel] " Glauber de Oliveira Costa
2007-11-07 13:27       ` Akio Takebe

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=1DC8211684B62Btakebe_akio@jp.fujitsu.com \
    --to=takebe_akio@jp.fujitsu.com \
    --cc=avi@qumranet.com \
    --cc=gcosta@redhat.com \
    --cc=hollisb@us.ibm.com \
    --cc=jeremy@goop.org \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox