Messages in this thread | | | Date | Thu, 3 May 2012 11:07:47 +0300 | Subject | Re: vmevent: question? | From | Pekka Enberg <> |
| |
On Thu, May 3, 2012 at 10:57 AM, Minchan Kim <minchan@kernel.org> wrote: > Sorry for my poor explanation. > My point is when userspace get vmevent_event by reading fd, it could enumerate > several attribute all at once. > Then, one of attribute(call A) made by vmevent_match in kernel and other attributes(call B, C, D) > are just extra for convenience. Because there is time gap when kernel get attribute values, B,C,D could be stale. > Then, how can user determine which event is really triggered? A or B or C or D? > Which event really happens?
Right. Mark the matching values with something like VMEVENT_ATTR_STATE_CAPTURED should be sufficient?
| |