qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: David Kiarie <davidkiarie4@gmail.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
	Valentine Sinitsyn <valentine.sinitsyn@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [V6 0/4] AMD IOMMU
Date: Mon, 22 Feb 2016 12:12:44 +0100	[thread overview]
Message-ID: <56CAED2C.4060700@web.de> (raw)
In-Reply-To: <CABdVeACa0SLmP=XymW=0=E4zr7-dcRgwKPAzCei55hp=Zq9ahQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1883 bytes --]

On 2016-02-22 12:05, David Kiarie wrote:
> On Mon, Feb 22, 2016 at 10:29 AM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> On 2016-02-22 06:57, David Kiarie wrote:
>>> On Sun, Feb 21, 2016 at 11:20 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>>>> On 2016-02-21 19:10, David Kiarie wrote:
>>>>> Hello there,
>>>>>
>>>>> Repost, AMD IOMMU patches version 6.
>>>>>
>>>>> Changes since version 5
>>>>>  -Fixed macro formating issues
>>>>>  -changed occurences of IO MMU to IOMMU for consistency
>>>>>  -Fixed capability registers duplication
>>>>>  -Rebased to current master
>>>>
>>>> I suspect this still has some subtle bugs: I'm running the patches over
>>>> master with standard Linux distro as guest, full desktop, and I'm
>>>> getting sporadic segfaults of arbitrary programs. These disappear once I
>>>> disable the IOMMU or switch to the Intel version.
>>>
>>> Is this L1 guest or L2 guest ? - haven't got any such so far.
>>
>> It's L1 only.
>>
>>>
>>>>
>>>> How did you test so far?
>>>
>>> I mainly test by logging. I've tested L1 without any iommu-related
>>> command line parameters and with L1 with 'iommu=1 iommu=pt'. L2 guest;
>>> passed-through a device checked it's working correctly, that all.
>>> These guests barely have any load though.
>>
>> I quickly reproduced the issue by starting some "heavier" applications,
>> a browser or an office suite. Something is apparently always corrupted
>> then, data or code, thus the crashes.
> 
> Can't reproduce this issue with my ubuntu/debian VMs. Are you using
> any iommu-related command line parameters ?

This is my command line:

qemu-system-x86_64
    -drive file=/path/to/64-bit-linux.img,discard=unmap,if=none,id=disk
    -device ide-hd,drive=disk -snapshot -m 1G -enable-kvm -smp 4
    -machine q35,iommu=amd

64-bit guest userland, linus.git head guest kernel.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-02-22 11:12 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-21 18:10 [Qemu-devel] [V6 0/4] AMD IOMMU David Kiarie
2016-02-21 18:10 ` [Qemu-devel] [V6 1/4] hw/i386: Introduce " David Kiarie
2016-02-25 15:43   ` Marcel Apfelbaum
2016-02-26  6:23     ` David Kiarie
2016-03-02  4:00       ` David Kiarie
2016-03-02  4:08         ` David Kiarie
2016-03-03  9:40           ` Marcel Apfelbaum
2016-03-03  9:34         ` Marcel Apfelbaum
2016-03-02 19:11     ` David Kiarie
2016-03-03 12:16       ` Marcel Apfelbaum
2016-02-21 18:10 ` [Qemu-devel] [V6 2/4] hw/core: Add AMD IOMMU to machine properties David Kiarie
2016-02-21 20:09   ` Jan Kiszka
2016-03-02 20:51     ` David Kiarie
2016-03-03  9:28       ` Marcel Apfelbaum
2016-03-11 13:20   ` Michael S. Tsirkin
2016-02-21 18:10 ` [Qemu-devel] [V6 3/4] hw/i386: ACPI table for AMD IOMMU David Kiarie
2016-02-21 18:20   ` Jan Kiszka
2016-02-21 19:00     ` David Kiarie
2016-02-21 18:11 ` [Qemu-devel] [V6 4/4] hw/pci-host: Emulate " David Kiarie
2016-02-22 11:22   ` Marcel Apfelbaum
     [not found]     ` <56D75688.1020500@gmail.com>
2016-03-02 21:17       ` Michael S. Tsirkin
2016-03-02 22:04         ` David Kiarie
2016-03-03  9:49           ` Michael S. Tsirkin
2016-03-03 11:47             ` David Kiarie
2016-03-03 12:02               ` Marcel Apfelbaum
2016-03-03 12:06                 ` Marcel Apfelbaum
2016-03-03 12:18                   ` David Kiarie
2016-03-03 12:58                     ` Michael S. Tsirkin
2016-03-08 17:15             ` David Kiarie
2016-03-11 13:22   ` Michael S. Tsirkin
2016-03-13  0:14     ` David Kiarie
2016-03-13 13:59       ` Michael S. Tsirkin
2016-02-21 20:20 ` [Qemu-devel] [V6 0/4] " Jan Kiszka
2016-02-22  5:57   ` David Kiarie
2016-02-22  7:29     ` Jan Kiszka
2016-02-22 11:05       ` David Kiarie
2016-02-22 11:12         ` Jan Kiszka [this message]
2016-03-01 13:07 ` Michael S. Tsirkin
2016-03-01 13:48   ` Jan Kiszka
2016-03-01 13:55     ` Michael S. Tsirkin
2016-03-01 14:12       ` Jan Kiszka
2016-03-01 14:18         ` Jan Kiszka
2016-03-01 14:30           ` Michael S. Tsirkin
2016-03-01 14:35             ` Jan Kiszka
2016-03-01 14:19         ` Michael S. Tsirkin
2016-03-01 14:00     ` Jan Kiszka
2016-03-01 20:11       ` Michael S. Tsirkin
2016-03-01 20:17         ` Jan Kiszka
2016-03-01 20:39           ` Michael S. Tsirkin
2016-03-01 21:23             ` Jan Kiszka
2016-03-01 22:35               ` Michael S. Tsirkin
2016-03-02 21:17     ` David Kiarie
2016-03-02 21:32       ` Michael S. Tsirkin

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=56CAED2C.4060700@web.de \
    --to=jan.kiszka@web.de \
    --cc=davidkiarie4@gmail.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=valentine.sinitsyn@gmail.com \
    /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).