Thorsten Glaser píše v Ne 13. 01. 2013 v 22:32 +0000: > >> The specs specifically say the contrary: they must be in virtual > >> addresses, but still in physical memory: > > > >specs is probably incorrect :-/ Where did you get the following quotes > >from? > > http://wiki.aranym.org/natfeats/proposal
"proposal"... Those were just ideas. The final implementation is different. Documentation needs to be corrected. > For detecting whether we run under virtualisation, this would have been > the way to go. In the very dark past NatFeats were meant to be called even from user space but later it was decided to use NatFeats from the kernel space only. Whatever needs to call host should use a device driver for that. And kernel space can work with physical (non-mapped) memory addresses easily thus providing the host with real contiguous memory blocks to read from/write to. Thanks to that host can use fast memcpy() when exchanging data with the guest. With logical (MMU mapped) addresses this wouldn't be possible because contiguous memory blocks would not be guaranteed. > Too bad if the specs are “incorrect” ☹ what you were trying was sort of NatFeat mis-use, anyway. Is user-space program supposed to do HW detection in Linux? I doubt it. Let the kernel detect hardware for you and then check /proc/hardware or so. > >I suppose the maintainer could grab the patch from CVS and apply it to > >ARAnyM in wheezy? Or I may prepare a 0.9.15 release of ARAnyM... > > I can probably NMU it, the maintainer isn’t a DD IIRC. Antonin Kral is (or has always been) a DD. > I think that, since a newer upstream version is in sid anyway, > we have to go through testing-proposed-updates already, so maybe > putting together a 0.9.15 with all fixes would be good, which we > can add to unstable, and I’ll apply the fix on top of 0.9.13 in > wheezy? I am all for putting together 0.9.15 for sid. Petr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
