Displaying 2 results from an estimated 2 matches for "spec_compliant_op".
Did you mean:
spec_compliant_ops
2020 Apr 30
0
[RFC/PATCH 1/1] virtio: Introduce MMIO ops
...> +#define virtio_writeb(val, a) mmio_ops->mmio_writeb((val), (a))
> +#define virtio_writew(val, a) 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 po...
2020 Apr 30
0
[RFC/PATCH 1/1] virtio: Introduce MMIO ops
...((val), (a))
> > > +#define virtio_writew(val, a) 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?
>
> If CONFIG_VIRTIO_MMIO_OPS is defined, then I expect this to be unconditionally
> set to 'magic_qcom_ops' that uses hypervisor-supported int...