From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Frediano Ziglio <frediano.ziglio@citrix.com>,
"Keir (Xen.org)" <keir@xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [RFC PATCH] Adding support for coverage informations
Date: Tue, 29 Jan 2013 11:47:24 +0000 [thread overview]
Message-ID: <5107B6CC.7040608@citrix.com> (raw)
In-Reply-To: <5107C38D02000078000BA5BB@nat28.tlf.novell.com>
On 29/01/13 11:41, Jan Beulich wrote:
>>>> On 29.01.13 at 11:56, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>> We might have some checks in the tree to ensure that non-init code
>> cannot reference init code by mistake -- maybe that's what broke the
>> build for you?
> No, (sadly) we don't have such checks in place.
>
> Jan
Linux has such checks. Would it be possible to beg/steal/borrow it in a
useful fashion?
With regards to the reentrant NMI issue, I was considering introducing
__nmi and __mce tags in a similar way to __init.
At one level, simply having the tags as noops to the compiler would at
least make programmers consider the implication of what they are
inserting into the codepaths, but if there is the ability to have
compiler checks to verify a base level of sanity, that is even better.
~Andrew
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-01-29 11:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 21:16 [RFC PATCH] Adding support for coverage informations Frediano Ziglio
2013-01-29 10:41 ` Jan Beulich
2013-01-29 12:58 ` Frediano Ziglio
2013-01-29 14:35 ` Jan Beulich
2013-01-29 10:56 ` Ian Campbell
2013-01-29 11:41 ` Jan Beulich
2013-01-29 11:47 ` Andrew Cooper [this message]
2013-01-29 11:51 ` Jan Beulich
2013-01-29 12:02 ` Frediano Ziglio
2013-01-30 9:59 ` Ian Campbell
2013-01-30 21:34 ` Konrad Rzeszutek Wilk
2013-01-31 8:51 ` Ian Campbell
2013-02-01 14:29 ` Frediano Ziglio
2013-02-01 14:46 ` Konrad Rzeszutek Wilk
2013-02-01 15:05 ` Frediano Ziglio
2013-02-01 20:54 ` Konrad Rzeszutek Wilk
2013-02-01 14:27 ` Frediano Ziglio
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=5107B6CC.7040608@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=frediano.ziglio@citrix.com \
--cc=keir@xen.org \
--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.