* [Qemu-devel] Trying to remove the TLB / What to do when device access fail with error code 2(not present)
[not found] <442432985.1323034.1475486616906.JavaMail.zimbra@imag.fr>
@ 2016-10-03 9:26 ` Antoine Faravelon
0 siblings, 0 replies; only message in thread
From: Antoine Faravelon @ 2016-10-03 9:26 UTC (permalink / raw)
To: qemu-devel
Good morning.
I am currently trying to replace the TLB entirely but fail to do so. Indeed, while I seem to have managed to catch any call/access made to it, whenever I now try to read or write to a device, I get a failed access(code is 2, e.g. device not present). My addresses do seem to be good. Which leads me to ask, what should I do when I get such a failed access? What can I do so that qemu somehow allocate or wire up the device access?
I work on x86_64 frontend and backend.
Thanks for your time,
Antoine.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-10-03 10:16 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <442432985.1323034.1475486616906.JavaMail.zimbra@imag.fr>
2016-10-03 9:26 ` [Qemu-devel] Trying to remove the TLB / What to do when device access fail with error code 2(not present) Antoine Faravelon
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).