Roman Kisel <rom...@linux.microsoft.com> writes: > Define what the confidential VMBus is and describe what advantages > it offers on the capable hardware. > > Signed-off-by: Roman Kisel <rom...@linux.microsoft.com> > Reviewed-by: Alok Tiwari <alok.a.tiw...@oracle.com> > --- > Documentation/virt/hyperv/coco.rst | 125 ++++++++++++++++++++++++++++- > 1 file changed, 124 insertions(+), 1 deletion(-) > > diff --git a/Documentation/virt/hyperv/coco.rst > b/Documentation/virt/hyperv/coco.rst > index c15d6fe34b4e..b4904b64219d 100644 > --- a/Documentation/virt/hyperv/coco.rst > +++ b/Documentation/virt/hyperv/coco.rst
[...] > + > +Here is the data flow for a conventional VMBus connection and the > Confidential > +VMBus connection (C stands for the client or VSC, S for the server or VSP): > + > ++---- GUEST ----+ +----- DEVICE ----+ +----- HOST -----+ > +| | | | | | > +| | | | | | > +| | | ========== | > +| | | | | | > +| | | | | | > +| | | | | | > ++----- C -------+ +-----------------+ +------- S ------+ This will generate all kinds of errors during the docs build and will not give the results you are looking for - please actually build the docs after making a change like this. You need to put the diagram into a literal block. Thanks, jon
