[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH] tools/xenstore: don't store domU's mfn of ring page in xensotred
On 28/04/2020 16:51, Juergen Gross wrote: > The XS_INTRODUCE command has two parameters: the mfn (or better: gfn) > of the domain's xenstore ring page and the event channel of the > domain for communicating with Xenstore. > > The gfn is not really needed. It is stored in the per-domain struct > in xenstored and in case of another XS_INTRODUCE for the domain it > is tested to match the original value. If it doesn't match the > command is aborted via EINVAL. > > Today there shouldn't be multiple XS_INTRODUCE requests for the same > domain issued, so the mfn/gfn can just be ignored and multiple > XS_INTRODUCE commands can be rejected without testing the mfn/gfn. > > Signed-off-by: Juergen Gross <jgross@xxxxxxxx> In hindsight, this is cleanup following c/s 38eeb3864d "tools/xenstored: Drop mapping of the ring via foreign map". Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |