public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
	x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git-pull -tip V2] x86: cpu architecture debug code
Date: Fri, 13 Mar 2009 00:34:36 -0700	[thread overview]
Message-ID: <49BA0C8C.4050302@goop.org> (raw)
In-Reply-To: <1236770749.2836.10.camel@ht.satnam>

Jaswinder Singh Rajput wrote:
>>> Complete diff:
>>> diff --git a/arch/x86/kernel/cpu/cpu_debug.c b/arch/x86/kernel/cpu/cpu_debug.c
>>> index 0bdf4da..08c365a 100755
>>> --- a/arch/x86/kernel/cpu/cpu_debug.c
>>> +++ b/arch/x86/kernel/cpu/cpu_debug.c
>>> @@ -464,19 +464,19 @@ static void print_dt(void *seq)
>>>  	unsigned long ldt;
>>>  
>>>  	/* IDT */
>>> -	store_idt((struct desc_ptr *)&dt);
>>> +	native_store_idt((struct desc_ptr *)&dt);
>>>       
>> hm, this wont work on Xen then.
>>
>>     
>
> Strange it should work for Xen, Are you getting any error.
>
> Xen also uses native_store_idt:
> arch/x86/xen/enlighten.c:	.store_idt = native_store_idt,
>   

store_idt (and the others) are not used very much, and never in any code 
path under Xen.  They're not really meaningful in Xen, and this code 
will probably oops if you ran it.

I guess we could do more meaningful implementations of these ops for 
Xen, now that there's a user.

>>>  	print_desc_ptr("IDT", seq, dt);
>>>  
>>>  	/* GDT */
>>> -	store_gdt((struct desc_ptr *)&dt);
>>> +	native_store_gdt((struct desc_ptr *)&dt);
>>>  	print_desc_ptr("GDT", seq, dt);
>>>  
>>>  	/* LDT */
>>> -	store_ldt(ldt);
>>> +	asm volatile("sldt %0" : "=m" (ldt));
>>>  	seq_printf(seq, " LDT\t: %016lx\n", ldt);
>>>  
>>>  	/* TR */
>>> -	store_tr(ldt);
>>> +	asm volatile("str %0" : "=r" (ldt));
>>>  	seq_printf(seq, " TR\t: %016lx\n", ldt);
>>>       
>> we do have a store_tr() primitive - why open code the assembly?
>>
>>     
>
> It is a single line code to avoid further conflicts, so i moved it here.
>   

Definitely a bad idea.

    J

  parent reply	other threads:[~2009-03-13  7:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 11:23 [git-pull -tip V2] x86: cpu architecture debug code Jaswinder Singh Rajput
2009-03-10 12:28 ` Ingo Molnar
2009-03-10 15:09   ` Jaswinder Singh Rajput
2009-03-10 15:20     ` Ingo Molnar
2009-03-10 16:09       ` Jaswinder Singh Rajput
2009-03-10 17:45         ` Ingo Molnar
2009-03-10 23:55           ` Jaswinder Singh Rajput
2009-03-11 10:53             ` Ingo Molnar
2009-03-11 11:25               ` Jaswinder Singh Rajput
2009-03-11 11:34                 ` Ingo Molnar
2009-03-13  7:34                 ` Jeremy Fitzhardinge [this message]
2009-03-13  8:07                   ` Jaswinder Singh Rajput
2009-03-11 11:54           ` Jaswinder Singh Rajput
2009-03-11 12:45             ` Jaswinder Singh Rajput
2009-03-11 12:50               ` Ingo Molnar
2009-03-11 13:13                 ` Ingo Molnar
2009-03-11 13:43                   ` Jaswinder Singh Rajput
2009-03-11 13:48                     ` Ingo Molnar
2009-03-13  7:37                     ` Jeremy Fitzhardinge
2009-03-10 17:48         ` [tip:x86/debug] " Jaswinder Singh Rajput
2009-03-10 19:53       ` [git-pull -tip V2] " Valdis.Kletnieks
2009-03-10 22:00         ` Ingo Molnar

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=49BA0C8C.4050302@goop.org \
    --to=jeremy@goop.org \
    --cc=hpa@zytor.com \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=x86@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