From: Simon Horman <horms@verge.net.au>
To: Tom Rotenberg <tom.rotenberg@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Possible bug with pass-through hot-plug?
Date: Mon, 19 Oct 2009 11:09:01 +0900 [thread overview]
Message-ID: <20091019020901.GG11338@verge.net.au> (raw)
In-Reply-To: <8686c3cd0910172220k25ba4f13kdb1ca1c6854d6fdd@mail.gmail.com>
Hi Tom,
On Sun, Oct 18, 2009 at 07:20:05AM +0200, Tom Rotenberg wrote:
> Simon,
>
> Just checked what u propsed, and it works.
I must confess that I am surprised. Good work :-)
> So, i'm pretty sure, that the problem is with the ASL code. I thought
> of an implementaion change of the ASL code, which will make it work:
> we will change it from:
> ...
> if ( slt == 0x1 )
> else if (slt == 0x2)
> ...
> else if (slt == 0x20)
> .,..
>
> to the following (just as an example):
> if ( slt < 0x10 )
> {
> if (slt == 0x1)
> ...
> } else {
> if ( slt == 0x11)
> ...
> }
>
> What do u think about this?
I think that could be a good attack. To be honest I haven't done
that much work with ASL, so I'm not sure how easy it would be
to implement anything more sophisticated than what you suggest.
The ASL code that you're hacking on was auto generated (off-line, by me)
(unless I'm mistaken). Auto generating the replacement is probably
a good idea. I can take a stab at that if you like, though time is
quite tight at the moment as I'm travelling and in meetings a lot,
so it might have to wait a week or so.
next prev parent reply other threads:[~2009-10-19 2:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 9:00 Possible bug with pass-through hot-plug? Tom Rotenberg
2009-10-07 9:38 ` Simon Horman
[not found] ` <8686c3cd0910070256p77f58aeat23aea646aaf82b86@mail.gmail.com>
[not found] ` <20091007120246.GA5088@verge.net.au>
2009-10-07 15:28 ` Tom Rotenberg
2009-10-07 15:41 ` Tom Rotenberg
2009-10-07 22:52 ` Simon Horman
2009-10-07 23:41 ` Simon Horman
2009-10-08 13:55 ` Tom Rotenberg
2009-10-08 22:36 ` Simon Horman
2009-10-09 8:36 ` Tom Rotenberg
2009-10-09 8:59 ` Simon Horman
2009-10-09 9:07 ` Simon Horman
2009-10-09 11:30 ` Tom Rotenberg
2009-10-09 11:47 ` Simon Horman
2009-10-09 11:49 ` Tom Rotenberg
2009-10-09 12:09 ` Simon Horman
2009-10-09 14:29 ` Tom Rotenberg
2009-10-10 1:41 ` Simon Horman
2009-10-11 9:57 ` Tom Rotenberg
2009-10-12 22:36 ` Simon Horman
2009-10-13 9:08 ` Tom Rotenberg
2009-10-13 9:43 ` Simon Horman
2009-10-13 9:52 ` Tom Rotenberg
2009-10-15 9:31 ` Simon Horman
2009-10-15 9:38 ` Tom Rotenberg
2009-10-15 11:06 ` Simon Horman
2009-10-15 14:02 ` Tom Rotenberg
2009-10-16 7:43 ` Simon Horman
2009-10-18 5:20 ` Tom Rotenberg
2009-10-19 2:09 ` Simon Horman [this message]
2009-10-19 2:27 ` Tom Rotenberg
2009-10-19 2:45 ` Simon Horman
2009-11-24 5:48 ` Simon Horman
2009-11-25 12:25 ` Tom Rotenberg
2009-11-26 13:54 ` Keir Fraser
2009-11-26 22:47 ` Simon Horman
2009-11-29 10:27 ` Tom Rotenberg
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=20091019020901.GG11338@verge.net.au \
--to=horms@verge.net.au \
--cc=tom.rotenberg@gmail.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.