Displaying 2 results from an estimated 2 matches for "register_virtio_mmio_op".
Did you mean:
register_virtio_mmio_ops
2020 Apr 30
0
[RFC/PATCH 1/1] virtio: Introduce MMIO ops
...->mmio_writew((val), (a))
> +#define virtio_writel(val, a) mmio_ops->mmio_writel((val), (a))
How exactly are these ops hooked up? I'm envisaging something like:
ops = spec_compliant_ops;
[...]
if (firmware_says_hypervisor_is_buggy())
ops = magic_qcom_ops;
am I wrong?
> +int register_virtio_mmio_ops(struct virtio_mmio_ops *ops)
> +{
> + pr_info("Registered %s as mmio ops\n", ops->name);
> + mmio_ops = ops;
Not looking good, and really defeats the point of standardising this stuff
imo.
Will
2020 Apr 30
0
[RFC/PATCH 1/1] virtio: Introduce MMIO ops
...nally
> set to 'magic_qcom_ops' that uses hypervisor-supported interface for IO (for
> example: message_queue_send() and message_queue_recevie() hypercalls).
Hmm, but then how would such a kernel work as a guest under all the
spec-compliant hypervisors out there?
> > > +int register_virtio_mmio_ops(struct virtio_mmio_ops *ops)
> > > +{
> > > + pr_info("Registered %s as mmio ops\n", ops->name);
> > > + mmio_ops = ops;
> >
> > Not looking good, and really defeats the point of standardising this stuff
> > imo.
>
> Ok. I guess the...