qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Artyom Tarasenko <atar4qemu@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Target-agnostic virtio?
Date: Sat, 27 Apr 2013 22:00:06 +0200	[thread overview]
Message-ID: <CACXAS8BFcKcrHMiKVeaoNKFZSga7jS6e1odXEQ+cbzhBqLRA+Q@mail.gmail.com> (raw)
In-Reply-To: <1366164953.18069.111@driftwood>

On Wed, Apr 17, 2013 at 4:15 AM, Rob Landley <rob@landley.net> wrote:
> On 04/14/2013 04:38:23 AM, Artyom Tarasenko wrote:
>>
>> On Sat, Apr 13, 2013 at 7:03 PM, Rob Landley <rob@landley.net> wrote:
>> > On 03/26/2013 02:34:50 AM, Artyom Tarasenko wrote:
>> >>
>> >> On Tue, Mar 26, 2013 at 1:52 AM, Rob Landley <rob@landley.net> wrote:
>> >> > Can the virtio things (serial, network, block, virtfs) be used on
>> >> > arbitrary
>> >> > targets yet? I.E. Can I use a virtio network device on arm, mips,
>> >> > powerpc,
>> >> > sparc...
>> >>
>> >> Yes. Moreover, for sparc64 the virtio network is currently the only
>> >> way to have a network under Linux guest (and a virtio block is the
>> >> only to have a disk under Linux guest).
>> >
>> >
>> > Do you have an example kernel .config and qemu command line showing how
>> > to
>> > use virtio for those? (Or a working sparc64 image you can point me to?)
>>
>> Yes. Will send it to you as I get to my home machine. Can you make them
>> available on your site?
>
> I plan to add a sparc64 target built from source to Aboriginal Linux.

Good to hear that. The more use/test cases, the less bugs!
Actually I was asking whether you would host a non-Aboriginal, foreign
Debian kernel.
But never mind, I figured it's better to fix QEMU to be able use a
vanilla Debian kernel
instead of building custom kernels. :-)

So if you have more than one PCI / virtio device in your
qemu-system-sparc64 setup, you
may want to update your QEMU to today's git master.

> For a lot of the 64-bit targets, actual 64 bit userspace support is
> strangely lacking. For ppc64 they say to use ppc32, and I've been told that
> about sparc64 as well. I don't know if this is an optimization or a
> requirement. I have a 32 bit image, I'd like to test the 64 bit codepaths as
> well...

I guess it's rather an optimisation. At least I saw BusyBox working under
QEMU before the sparc v8plus was fixed.

Artyom

--
Regards,
Artyom Tarasenko

linux/sparc and solaris/sparc under qemu blog:
http://tyom.blogspot.com/search/label/qemu

  parent reply	other threads:[~2013-04-27 20:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26  0:52 [Qemu-devel] Target-agnostic virtio? Rob Landley
2013-03-26  1:24 ` Richard Henderson
2013-03-26  3:55   ` Rob Landley
2013-03-26  7:34 ` Artyom Tarasenko
2013-04-13 17:03   ` Rob Landley
2013-04-14  9:38     ` Artyom Tarasenko
2013-04-14  9:59       ` Mark Cave-Ayland
2013-04-14 19:49         ` Artyom Tarasenko
2013-04-15 17:21           ` Rob Landley
2013-04-17  2:15       ` Rob Landley
2013-04-20 10:36         ` Blue Swirl
2013-04-21  5:37           ` Rob Landley
2013-04-27 20:00         ` Artyom Tarasenko [this message]
2013-04-29  5:43           ` Rob Landley
2013-04-30 21:31             ` Artyom Tarasenko
2013-05-01 17:12               ` Rob Landley

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=CACXAS8BFcKcrHMiKVeaoNKFZSga7jS6e1odXEQ+cbzhBqLRA+Q@mail.gmail.com \
    --to=atar4qemu@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rob@landley.net \
    /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;
as well as URLs for NNTP newsgroup(s).