Jan Beulich:
On 23.05.18 at 00:21, wrote:
>> I have done some more testing in the meantime. The issue also affect
>> 4.10.1, but not 4.10.0. That's useful since it makes the bisect shorter.
>> A bisect identifies 8462c575d9 "x86/xpti: Hide almost all of .text and
>> all .data/.rodata/.bss map
>>> On 23.05.18 at 00:21, wrote:
> I have done some more testing in the meantime. The issue also affect
> 4.10.1, but not 4.10.0. That's useful since it makes the bisect shorter.
> A bisect identifies 8462c575d9 "x86/xpti: Hide almost all of .text and
> all .data/.rodata/.bss mappings" as the comm
George Dunlap:
> On Fri, May 18, 2018 at 5:19 PM, Marek Marczykowski
> wrote:
>> On Fri, May 18, 2018 at 09:54:37AM -0600, Jan Beulich wrote:
>> On 18.05.18 at 17:33, wrote:
Yes, I'm happy to help with that. As I've said, the basic test is very
simple (rtcwake command) and already v
On Mon, 2018-05-21 at 14:57 +0100, Ian Jackson wrote:
> > On Mon, 2018-05-21 at 12:04 +0100, George Dunlap wrote:
> > > What if we 1) have two versions of the test -- "Fake suspend" and
> > > "Real Suspend"; 2) only run "Real suspend" on hardware
> > > specifically
> > > marked as having a suspend
On Mon, May 21, 2018 at 5:28 PM, George Dunlap wrote:
> On Mon, May 21, 2018 at 5:17 PM, Andrew Cooper
> wrote:
>> On 21/05/18 16:48, George Dunlap wrote:
>>> On Fri, May 18, 2018 at 5:19 PM, Marek Marczykowski
>>> wrote:
On Fri, May 18, 2018 at 09:54:37AM -0600, Jan Beulich wrote:
On Mon, May 21, 2018 at 5:17 PM, Andrew Cooper
wrote:
> On 21/05/18 16:48, George Dunlap wrote:
>> On Fri, May 18, 2018 at 5:19 PM, Marek Marczykowski
>> wrote:
>>> On Fri, May 18, 2018 at 09:54:37AM -0600, Jan Beulich wrote:
>>> On 18.05.18 at 17:33, wrote:
> Yes, I'm happy to help with
On 21/05/18 16:48, George Dunlap wrote:
> On Fri, May 18, 2018 at 5:19 PM, Marek Marczykowski
> wrote:
>> On Fri, May 18, 2018 at 09:54:37AM -0600, Jan Beulich wrote:
>> On 18.05.18 at 17:33, wrote:
Yes, I'm happy to help with that. As I've said, the basic test is very
simple (rtcwa
On Fri, May 18, 2018 at 5:19 PM, Marek Marczykowski
wrote:
> On Fri, May 18, 2018 at 09:54:37AM -0600, Jan Beulich wrote:
>> >>> On 18.05.18 at 17:33, wrote:
>> > Yes, I'm happy to help with that. As I've said, the basic test is very
>> > simple (rtcwake command) and already very useful. The fact
On Mon, May 21, 2018 at 2:57 PM, Ian Jackson wrote:
> Dario Faggioli writes ("Re: [Xen-devel] Test for osstest, features used in
> Qubes OS"):
>> On Mon, 2018-05-21 at 12:04 +0100, George Dunlap wrote:
>> > What if we 1) have two versions of the test -- "Fake
Dario Faggioli writes ("Re: [Xen-devel] Test for osstest, features used in
Qubes OS"):
> On Mon, 2018-05-21 at 12:04 +0100, George Dunlap wrote:
> > What if we 1) have two versions of the test -- "Fake suspend" and
> > "Real Suspend"; 2) only run "
On Mon, 2018-05-21 at 12:04 +0100, George Dunlap wrote:
> On Thu, May 17, 2018 at 4:12 PM, Ian Jackson
> wrote:
> > That's not entirely trivial then, especially for you, unless you
> > want
> > to set up your own osstest production instance. However, I can
> > probably do the osstest-machinery wo
On Thu, 2018-05-17 at 16:12 +0100, Ian Jackson wrote:
> Marek Marczykowski-Górecki writes ("Re: Test for osstest, features
> used in Qubes OS"):
> > On Thu, May 17, 2018 at 01:26:30PM +0100, Ian Jackson wrote:
> > > Is it likely that this will depend on non-buggy host firmware
> > > ? If so
> > >
On Thu, May 17, 2018 at 4:12 PM, Ian Jackson wrote:
> Marek Marczykowski-Górecki writes ("Re: Test for osstest, features used in
> Qubes OS"):
>> On Thu, May 17, 2018 at 01:26:30PM +0100, Ian Jackson wrote:
>> > Is it likely that this will depend on non-buggy host firmware ? If so
>> > then we n
On Fri, May 18, 2018 at 09:54:37AM -0600, Jan Beulich wrote:
> >>> On 18.05.18 at 17:33, wrote:
> > Yes, I'm happy to help with that. As I've said, the basic test is very
> > simple (rtcwake command) and already very useful. The fact that it is(?)
> > broken on staging doesn't make it easier,
>
>
>>> On 18.05.18 at 17:33, wrote:
> Yes, I'm happy to help with that. As I've said, the basic test is very
> simple (rtcwake command) and already very useful. The fact that it is(?)
> broken on staging doesn't make it easier,
Details on the breakage would be appreciated (on a separate thread),
unl
On Thu, May 17, 2018 at 08:00:38PM +0200, Sander Eikelenboom wrote:
> Marek / Ian,
>
> Nice to see PCI-passthrough getting some attention again.
>
> On 17/05/18 17:12, Ian Jackson wrote:
> > Marek Marczykowski-Górecki writes ("Re: Test for osstest, features used in
> > Qubes OS"):
> >> On Thu, M
On Thu, May 17, 2018 at 04:12:09PM +0100, Ian Jackson wrote:
> Marek Marczykowski-Górecki writes ("Re: Test for osstest, features used in
> Qubes OS"):
> > On Thu, May 17, 2018 at 01:26:30PM +0100, Ian Jackson wrote:
> > > Is it likely that this will depend on non-buggy host firmware ? If so
> >
Marek / Ian,
Nice to see PCI-passthrough getting some attention again.
On 17/05/18 17:12, Ian Jackson wrote:
> Marek Marczykowski-Górecki writes ("Re: Test for osstest, features used in
> Qubes OS"):
>> On Thu, May 17, 2018 at 01:26:30PM +0100, Ian Jackson wrote:
>>> Is it likely that this will
Marek Marczykowski-Górecki writes ("Re: Test for osstest, features used in
Qubes OS"):
> On Thu, May 17, 2018 at 01:26:30PM +0100, Ian Jackson wrote:
> > Is it likely that this will depend on non-buggy host firmware ? If so
> > then we need to make arrangements to test it and only do it on hosts
On Thu, May 17, 2018 at 01:26:30PM +0100, Ian Jackson wrote:
> Marek Marczykowski-Górecki writes ("Test for osstest, features used in Qubes
> OS"):
> > As discussed some time ago, I'd like to help with adding tests for some
> > features we use in Qubes OS.
> >
> > IMO the easiest thing to test is
Marek Marczykowski-Górecki writes ("Test for osstest, features used in Qubes
OS"):
> As discussed some time ago, I'd like to help with adding tests for some
> features we use in Qubes OS.
>
> IMO the easiest thing to test is host suspend. You just need to execute
> "rtcwake -s 30 -m mem", and see
Hi,
As discussed some time ago, I'd like to help with adding tests for some
features we use in Qubes OS.
IMO the easiest thing to test is host suspend. You just need to execute
"rtcwake -s 30 -m mem", and see if the host is back to live after ~30s.
Right now I know it works on Xen 4.8, but suppos
22 matches
Mail list logo
