From: Christian Borntraeger <borntraeger@de.ibm.com>
To: David Woodhouse <dwmw2@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
linux-kernel@vger.kernel.org
Cc: Joerg Roedel <jroedel@suse.de>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Christoph Hellwig <hch@lst.de>,
benh@kernel.crashing.org, KVM <kvm@vger.kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] virtio_ring: Support DMA APIs
Date: Wed, 28 Oct 2015 17:39:43 +0900 [thread overview]
Message-ID: <563089CF.10001@de.ibm.com> (raw)
In-Reply-To: <1446012277.3405.179.camel@infradead.org>
Am 28.10.2015 um 15:04 schrieb David Woodhouse:
> On Wed, 2015-10-28 at 14:52 +0900, Christian Borntraeger wrote:
>> 000000000059b25a: e32010200004 lg %r2,32(%r1)
>> #000000000059b260: e310b0a00004 lg %r1,160(%r11)
>> >000000000059b266: 4810100c lh %r1,12(%r1)
>
> Precisely what is that? Is that loading ->archdata.dev_ops (offset 160)
> from a device and then trying to find the ->unmap_page method therein?
>
qemu 2.4 works, and current qemu master has a broken gdb server....I am going to fix
this first.
What I can tell, that the problem goes away if I disable virtio 1.0 so I assume
that things are fine when Andy sends a v4 with the endianess fixes.
Christian
next prev parent reply other threads:[~2015-10-28 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 5:30 [PATCH v2 0/3] virtio DMA API core stuff Andy Lutomirski
2015-10-28 5:30 ` [PATCH v2 1/3] virtio_net: Stop doing DMA from the stack Andy Lutomirski
2015-10-28 7:07 ` Michael S. Tsirkin
2015-10-29 23:43 ` Andy Lutomirski
2015-10-28 5:30 ` [PATCH v2 2/3] virtio_ring: Support DMA APIs Andy Lutomirski
2015-10-28 5:52 ` Christian Borntraeger
2015-10-28 6:04 ` David Woodhouse
2015-10-28 8:39 ` Christian Borntraeger [this message]
2015-10-28 5:30 ` [PATCH v2 3/3] virtio_pci: Use the DMA API Andy Lutomirski
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=563089CF.10001@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=cornelia.huck@de.ibm.com \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=luto@kernel.org \
--cc=pbonzini@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@linux.vnet.ibm.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).