Displaying 7 results from an estimated 7 matches for "nonono".
Did you mean:
nonon
2015 Oct 28
2
[PATCH v3 0/3] virtio DMA API core stuff
On Wed, Oct 28, 2015 at 10:35:27PM +0900, David Woodhouse wrote:
> On Wed, 2015-10-28 at 13:35 +0200, Michael S. Tsirkin wrote:
> > E.g. on intel x86, there's an option iommu=pt which does the 1:1
> > thing for devices when used by kernel, but enables
> > the iommu if used by userspace/VMs.
>
> That's none of your business.
>
> You call the DMA API when
2015 Oct 28
2
[PATCH v3 0/3] virtio DMA API core stuff
On Wed, Oct 28, 2015 at 10:35:27PM +0900, David Woodhouse wrote:
> On Wed, 2015-10-28 at 13:35 +0200, Michael S. Tsirkin wrote:
> > E.g. on intel x86, there's an option iommu=pt which does the 1:1
> > thing for devices when used by kernel, but enables
> > the iommu if used by userspace/VMs.
>
> That's none of your business.
>
> You call the DMA API when
2015 Oct 28
0
[PATCH v3 0/3] virtio DMA API core stuff
...not second-guess it.
(From the other mail)
> > > OK so I guess that means we should prefer a transport-specific
> > > interface in virtio-pci then.
> >
> > Why?
>
> Because you said you are doing something device tree specific for
> ARM, aren't you?
Nonono. The ARM platform code might do that, and the DMA API on ARM
*might* give you I/O virtual addresses that look a lot like the
physical addresses you asked it to map. That's none of your business.
Drivers use DMA API. No more talky.
--
dwmw2
-------------- next part --------------
A non-text...
2003 Oct 03
4
foo.RData or foo.r?
Dear All,
I suspect this is kind of dumb, but when I was under the thrall of the
dark lord (read, using a W2K box), all my work in R files came out as
foo.RData. I moved on to GNU/Linux, and all the old .RData files keep on
working as they used. No problems in loading and stuff. But I use R from
the terminal. Assuming I decide to switch to emacs, do I need to save my
work as foo.r? what about my
2015 Oct 28
2
[PATCH v3 0/3] virtio DMA API core stuff
...> > > > OK so I guess that means we should prefer a transport-specific
> > > > interface in virtio-pci then.
> > >
> > > Why?
> >
> > Because you said you are doing something device tree specific for
> > ARM, aren't you?
>
> Nonono. The ARM platform code might do that, and the DMA API on ARM
> *might* give you I/O virtual addresses that look a lot like the
> physical addresses you asked it to map. That's none of your business.
> Drivers use DMA API. No more talky.
Well for virtio they don't ATM. And 1:1 mapp...
2015 Oct 28
2
[PATCH v3 0/3] virtio DMA API core stuff
...> > > > OK so I guess that means we should prefer a transport-specific
> > > > interface in virtio-pci then.
> > >
> > > Why?
> >
> > Because you said you are doing something device tree specific for
> > ARM, aren't you?
>
> Nonono. The ARM platform code might do that, and the DMA API on ARM
> *might* give you I/O virtual addresses that look a lot like the
> physical addresses you asked it to map. That's none of your business.
> Drivers use DMA API. No more talky.
Well for virtio they don't ATM. And 1:1 mapp...
2023 Nov 10
0
A proper way to modify battery.charge.low persistently
...tead evaluate
the threshold in software, based on an override option
Another thing that took me a while was to realize, how the whole
graceful shutdown process is going. The process isn't nearly as
straightforward as it may seem at a first glance: "Battery low, SNAP,
lights out". Nonono.
The sequence is described in quite some detail in official
documentation (link to "configuration notes" follows below).
In rough outlines, in a standalone setup, the process goes like:
1) the power goes out, which the UPS signals to the server.
You get a message on the console and...