From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: [PATCH] Re: odd vcpu_info accesses in xen/arch/x86/time.c
Date: Thu, 31 Aug 2006 10:08:14 +0200 [thread overview]
Message-ID: <44F6B50E.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C11B7AF1.184B%Keir.Fraser@cl.cam.ac.uk>
>>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 30.08.06 18:27 >>>
>On 29/8/06 3:56 pm, "Jan Beulich" <jbeulich@novell.com> wrote:
>
>> Is there a particular reason why in several places in this file, with a vcpu
>> pointer
>> at hand, the vcpu_info is accessed through
>>
>> v->domain->shared_info->vcpu_info[v->vcpu_id]
>>
>> rather than
>>
>> v->vcpu_info
>
>No. They should be fixed.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Index: 2006-08-28/xen/arch/x86/time.c
===================================================================
--- 2006-08-28.orig/xen/arch/x86/time.c 2006-08-31 09:52:31.000000000 +0200
+++ 2006-08-28/xen/arch/x86/time.c 2006-08-31 09:55:54.000000000 +0200
@@ -676,7 +676,7 @@ static inline void __update_vcpu_system_
struct vcpu_time_info *u;
t = &this_cpu(cpu_time);
- u = &v->domain->shared_info->vcpu_info[v->vcpu_id].time;
+ u = &v->vcpu_info->time;
version_update_begin(&u->version);
@@ -690,7 +690,7 @@ static inline void __update_vcpu_system_
void update_vcpu_system_time(struct vcpu *v)
{
- if ( v->domain->shared_info->vcpu_info[v->vcpu_id].time.tsc_timestamp !=
+ if ( v->vcpu_info->time.tsc_timestamp !=
this_cpu(cpu_time).local_tsc_stamp )
__update_vcpu_system_time(v);
}
prev parent reply other threads:[~2006-08-31 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 14:56 odd vcpu_info accesses in xen/arch/x86/time.c Jan Beulich
2006-08-30 16:27 ` Keir Fraser
2006-08-31 8:08 ` Jan Beulich [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=44F6B50E.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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 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.