Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "Kevin D. Kissell" <KevinK@paralogos.com>,
	Brian Foster <brian.foster@innova-card.com>,
	linux-mips@linux-mips.org, Andrew Dyer <adyer@righthandtech.com>
Subject: Re: Adding(?) XI support to MIPS-Linux?
Date: Wed, 11 Jun 2008 11:35:50 +0200	[thread overview]
Message-ID: <484F9C76.4030104@mips.com> (raw)
In-Reply-To: <20080611090601.GB19755@linux-mips.org>

Ralf Baechle wrote:
> On Mon, Jun 09, 2008 at 09:32:59PM +0200, Kevin D. Kissell wrote:
>
>   
>> That is correct, though there has long been interest in having XI/RI as an option for non-SmartMIPS cores and I would not be surprised if sooner or later it became more generally available.
>>     
>
> Cavium has it in their 64-bit core.  I haven't verified this in the docs
> but apparently it is meant to be compatible with the old SmartMIPS ASE
> for MIPS32.
>   
Do check the documentation.  I can't comment officially, but I can 
observe that,
in the hypothetical case where you'd want XI/RI semantics in a 64-bit 
processor,
you might use exactly the same semantics (and therefore the same kernel 
C code
support), but you might want to use different bits  for XI/RI in a 
64-bit TLB entry
than in a 32-bit TLB entry (and therefore different header file 
definitions).

          Regards,

          Kevin K.

  reply	other threads:[~2008-06-11  9:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200806091658.10937.brian.foster@innova-card.com>
2008-06-09 15:37 ` Re: Adding(?) XI support to MIPS-Linux? Brian Foster
2008-06-09 19:32   ` Kevin D. Kissell
2008-06-09 20:46     ` Thiemo Seufer
     [not found]       ` <200806101119.06227.brian.foster@innova-card.com>
2008-06-10  9:32         ` Brian Foster
2008-06-10  9:57           ` Thiemo Seufer
2008-06-10 16:21             ` David Daney
2008-06-11 13:16               ` Brian Foster
2008-06-11 18:51                 ` Kevin D. Kissell
2008-06-12 12:03                   ` Brian Foster
2008-06-18  8:42                 ` Brian Foster
2008-06-18  9:36                   ` Kevin D. Kissell
2008-06-18  9:45                     ` Brian Foster
2008-06-11  9:06     ` Ralf Baechle
2008-06-11  9:35       ` Kevin D. Kissell [this message]
     [not found] <200806091050.m59AoUUl014012@smtp02.msg.oleane.net>
2008-06-09 10:55 ` Brian Foster

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=484F9C76.4030104@mips.com \
    --to=kevink@mips.com \
    --cc=KevinK@paralogos.com \
    --cc=adyer@righthandtech.com \
    --cc=brian.foster@innova-card.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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