From: Guenter Roeck <linux@roeck-us.net>
To: sparclinux@vger.kernel.org
Subject: Re: [v1 0/2] Early boot timestamp fixes
Date: Thu, 15 Jun 2017 21:36:28 +0000 [thread overview]
Message-ID: <20170615213628.GB30058@roeck-us.net> (raw)
In-Reply-To: <1497537659-419752-1-git-send-email-pasha.tatashin@oracle.com>
On Thu, Jun 15, 2017 at 06:57:30PM +0100, Mark Cave-Ayland wrote:
> On 15/06/17 16:43, Pasha Tatashin wrote:
>
> > I have not used qemu for SPARC, so I am not fully aware of its
> > capability. The changes in this work touched three types of CPUs:
>
> The default CPU in QEMU for sun4u is the TI UltraSparc IIi, and the
> device tree is roughly similar to that of an Ultra 5, or it least it
> will be soon when I've finished working on my latest round of patches.
>
> Currently I'm booting one of John Paul Adrian Glaubitz's Debian 9 images
> and the timestamps stay at 0 until the clock is initialised so I'd hope
> that these patches would fix that. Do they require any PROM support at all?
>
> > 1. UltraSPARC IIe (Hummingbird)
> > - %stick is in I/O space, need at least to loads to get upper
> > and lower part of stick value.
> > 2. Spitfire
> > - Use %tick and cpu frequency to determine that clock. This is
> > what you tested with TI UltraSparc IIi
>
> So this is the path I'd expect to be exercised under QEMU.
>
> > 3. All other
> > - use %stick register and stick-frequency values. This is what
> > you tested with Fujitsu Sparc64 IV (which by the way is still
> > sun4u, I do not think qemu supports sun4v emulation)
>
> Sure it does. As of the latest 2.9 release, QEMU includes niagara
> support out of the box - see http://wiki.qemu.org/SPARC for the latest
Do you have information on how to boot the Linux kernel for -M niagara
(assuming that is possible) ? Directions for Solaris and HelenOS don't
help much for the uninitiated :-(.
Thanks,
Guenter
> updates and
> http://tyom.blogspot.co.uk/2016/10/qemu-sun4vniagara-target-went-public.html
> for more sun4v detail.
>
> Disclaimer: I'm one of the QEMU SPARC maintainers.
>
>
> ATB,
>
> Mark.
>
next prev parent reply other threads:[~2017-06-15 21:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 14:40 [v1 0/2] Early boot timestamp fixes Pavel Tatashin
2017-06-15 15:20 ` Guenter Roeck
2017-06-15 15:21 ` David Miller
2017-06-15 15:23 ` David Miller
2017-06-15 15:34 ` Pasha Tatashin
2017-06-15 15:43 ` Pasha Tatashin
2017-06-15 17:57 ` Mark Cave-Ayland
2017-06-15 18:06 ` David Miller
2017-06-15 19:36 ` Guenter Roeck
2017-06-15 20:01 ` Pasha Tatashin
2017-06-15 20:33 ` Guenter Roeck
2017-06-15 21:36 ` Guenter Roeck [this message]
2017-06-16 12:17 ` Mark Cave-Ayland
2017-06-16 12:23 ` Mark Cave-Ayland
2017-06-16 16:40 ` David Miller
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=20170615213628.GB30058@roeck-us.net \
--to=linux@roeck-us.net \
--cc=sparclinux@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 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.