All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tim Deegan <tim@xen.org>, Julien Grall <julien.grall@arm.com>,
	Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] xen: only clobber multicall elements without error
Date: Mon, 26 Nov 2018 15:40:13 +0000	[thread overview]
Message-ID: <23548.5085.66289.477986@mariner.uk.xensource.com> (raw)
In-Reply-To: <b8bc03f0-d305-951d-b11d-d44caa9b61f9@suse.com>

Juergen Gross writes ("Re: [PATCH] xen: only clobber multicall elements without error"):
> On 26/11/2018 15:54, Ian Jackson wrote:
> > Maybe they could be clobbered losslessly ?  Eg, by xoring with 0xaa or
> > something.
> 
> This would be rather hacky: I'd need to find out if clobbering was
> performed or not and the way of clobbering would be kind of an interface
> which I guess we'd like to avoid.

You can bake the precise method of clobbering into your kernel
debugging dump stuff, along with a mechanism which guesses whether
things have been clobbered, so long as you don't go utterly wrong if
your guesses are wrong.

Since after all Xen doesn't guarantee to preserve the arguments at
all, and therefore you mustn't rely on it anyway.

This seems fine for a debug dump mechanism - debug dump mechanisms are
generally best effort anyway.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-11-26 15:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 13:25 [PATCH] xen: only clobber multicall elements without error Juergen Gross
2018-11-23 13:28 ` Andrew Cooper
2018-11-23 13:40   ` Juergen Gross
2018-11-26 10:58 ` Jan Beulich
2018-11-26 14:54   ` Ian Jackson
2018-11-26 15:25     ` Juergen Gross
2018-11-26 15:40       ` Ian Jackson [this message]
     [not found] ` <5BFBD1C602000078001FFE09@suse.com>
2018-11-26 13:52   ` Juergen Gross
2018-11-26 14:01     ` Jan Beulich
     [not found]     ` <5BFBFCD3020000780020004F@suse.com>
2018-11-26 14:23       ` Juergen Gross
2018-11-26 14:58         ` Jan Beulich
     [not found]         ` <5BFC0A1302000078002000E1@suse.com>
     [not found]           ` <06592737*411f*d518*d972*6b4cdc704d9b@suse.com>
2018-11-26 15:29           ` Juergen Gross
2018-11-26 16:01             ` Julien Grall
2018-11-26 16:17               ` Juergen Gross
2018-11-26 16:50                 ` Jan Beulich
     [not found]                 ` <5BFC2462020000780020022A@suse.com>
2018-11-27  7:37                   ` Juergen Gross
2018-11-27  9:24                     ` Jan Beulich
2018-11-26 16:51 Julien Grall
2018-11-27  7:34 Juergen Gross
2018-11-27  9:16 Julien Grall
2018-11-27  9:25 Juergen Gross
2018-11-27  9:28 Juergen Gross

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=23548.5085.66289.477986@mariner.uk.xensource.com \
    --to=ian.jackson@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jgross@suse.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.