All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: moftah moftah <mofta7y@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: xen-ringwatch issues
Date: Mon, 12 Jan 2015 09:49:39 +0000	[thread overview]
Message-ID: <1421056179.26317.6.camel@citrix.com> (raw)
In-Reply-To: <CAPFC4Ry_eBw23n57Tu71mzgvgJQ8TBPN+_g9uccU5Dhcc+hjtA@mail.gmail.com>

On Fri, 2015-01-09 at 17:00 -0500, moftah moftah wrote:
> Hi Ian,
> 
> 
> OK, I have followed your suggestions and created a new patch

Thanks, please submit it in the form describe in the wiki page
http://wiki.xen.org/wiki/Submitting_Xen_Patches which I referenced
before.

In particular, a Signed-off-by is a strict requirement for licensing
reasons, to indicate that you have read the DCO (which is at
http://wiki.xen.org/wiki/Submitting_Xen_Patches#Signing_off_a_patch ).

Please also provide a suitable changelog entry and use a unified diff
(diff -u).

I think rather than "[-]*" the right addition would be -? (i.e. a single
optional negative sign), unless Python's re syntax is lots different to
what I expect.

> this new patch does fix the issue fully for the negative numbers
>
> I didnt run the patch on 64bit OS since xenserver has 32bit Dom0

These fields are unsigned int, .i.e. always 32-bits. So I think your "if
self.conf < 0: self.cons = 4294967296 + self.cons" etc will work. The
Internet also suggests "ctypes.c_uint32(i).value", dunno if that is
better. In any case writing 4294967296 as 2**32 would be slightly
clearer.

Ian.

      reply	other threads:[~2015-01-12  9:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08 19:07 xen-ringwatch issues moftah moftah
2015-01-09 10:10 ` Ian Campbell
2015-01-09 22:00   ` moftah moftah
2015-01-12  9:49     ` Ian Campbell [this message]

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=1421056179.26317.6.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=mofta7y@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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.