All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 10 of 15] xenpaging: compare both token and path when checking for @releaseDomain event
Date: Tue, 25 Oct 2011 20:02:39 +0200	[thread overview]
Message-ID: <20111025180239.GA14805@aepfle.de> (raw)
In-Reply-To: <20134.62630.115259.632324@mariner.uk.xensource.com>

On Tue, Oct 25, Ian Jackson wrote:

> Olaf Hering writes ("[Xen-devel] [PATCH 10 of 15] xenpaging: compare both token and path when checking for @releaseDomain event"):
> > xenpaging: compare both token and path when checking for @releaseDomain event
> > 
> > Subsequent patches will use xenstored to store the numbers of pages
> > xenpaging is suppose to page-out. A domain_id value could be
> > misinterpreted as number of pages. Compare both path and token to
> > recognize the @releaseDomain event.
> 
> I'm not sure I understand.  What are you currently using as the
> token ?  The token as well as the path should be sufficient to be able
> to tell what the event is, so this patch makes me suspicious ...

I was under the impression there could be identical tokens for different
paths, and that the actual value of the watched path is part of
XS_WATCH_TOKEN.  So this patch tries to make the detection of the
@releaseDomain event more robust.

But since the token seems to be unique (docs/misc/xenstore.txt has no
further description of 'token'), only the DPRINTF part of my patch
should be kept.

Please drop this change, I will add the DPRINTF in a separate patch.

Olaf

  reply	other threads:[~2011-10-25 18:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21  9:31 [PATCH 00 of 15] tools/xenpaging fixes for xen-unstable Olaf Hering
2011-10-21  9:31 ` [PATCH 01 of 15] xenpaging: remove filename from comment Olaf Hering
2011-10-21  9:31 ` [PATCH 02 of 15] xenpaging: remove obsolete comment in resume path Olaf Hering
2011-10-21  9:31 ` [PATCH 03 of 15] xenpaging: use PERROR to print errno Olaf Hering
2011-10-21  9:31 ` [PATCH 04 of 15] xenpaging: simplify file_op Olaf Hering
2011-10-21  9:31 ` [PATCH 05 of 15] xenpaging: print gfn in failure case Olaf Hering
2011-10-21  9:31 ` [PATCH 06 of 15] xenpaging: update xenpaging_init Olaf Hering
2011-10-21  9:31 ` [PATCH 07 of 15] xenpaging: remove xc_dominfo_t from paging_t Olaf Hering
2011-10-21  9:31 ` [PATCH 08 of 15] xenpaging: track the number of paged-out pages Olaf Hering
2011-10-21  9:31 ` [PATCH 09 of 15] xenpaging: move page add/resume loops into its own function Olaf Hering
2011-10-21  9:31 ` [PATCH 10 of 15] xenpaging: compare both token and path when checking for @releaseDomain event Olaf Hering
2011-10-25 17:40   ` Ian Jackson
2011-10-25 18:02     ` Olaf Hering [this message]
2011-10-25 18:13       ` Ian Jackson
2011-10-21  9:31 ` [PATCH 11 of 15] xenpaging: improve mainloop exit handling Olaf Hering
2011-10-21  9:31 ` [PATCH 12 of 15] libxc: add bitmap_clear function Olaf Hering
2011-10-21  9:31 ` [PATCH 13 of 15] xenpaging: retry unpageable gfns Olaf Hering
2011-10-21  9:31 ` [PATCH 14 of 15] xenpaging: install into LIBEXEC dir Olaf Hering
2011-10-21  9:31 ` [PATCH 15 of 15] xenpaging: add XEN_PAGING_DIR / libxl_xenpaging_dir_path() Olaf Hering

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111025180239.GA14805@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.