public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Jeremy Fitzhardinge <jeremy@goop.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 13:37:48 +0530	[thread overview]
Message-ID: <1236931668.7865.4.camel@ht.satnam> (raw)
In-Reply-To: <49BA0C8C.4050302@goop.org>

On Fri, 2009-03-13 at 00:34 -0700, Jeremy Fitzhardinge wrote:
> 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.
> 

cpu_debug is availabe in -tip.

Can you test it:

[jaswinder@ht linux-2.6-tip]$ cat /sys/kernel/debug/x86/cpu/cpu*/dt/dt
 IDT	: 00000000c05617ff
 GDT	: 00000000c17040ff
 LDT	: 0000000000000000
 TR	: 0000000000000080

 IDT	: 00000000c05617ff
 GDT	: 00000000c17140ff
 LDT	: 00000000fce90000
 TR	: 0000000000000080

[jaswinder@ht linux-2.6-tip]$ 


--
JSR


  reply	other threads:[~2009-03-13  8:09 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
2009-03-13  8:07                   ` Jaswinder Singh Rajput [this message]
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=1236931668.7865.4.camel@ht.satnam \
    --to=jaswinder@kernel.org \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.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