xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dfaggioli@suse.com>
To: George Dunlap <dunlapg@umich.edu>, Ian Jackson <ian.jackson@citrix.com>
Cc: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: Test for osstest, features used in Qubes OS
Date: Mon, 21 May 2018 13:52:15 +0200	[thread overview]
Message-ID: <b713974db1f90fcf450ce232761dab0defb3ee8a.camel@suse.com> (raw)
In-Reply-To: <CAFLBxZbubeqBGJ3=qhzxKVoQGakyaY2Hi8dMfXz+QeGLtZZeNA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2110 bytes --]

On Mon, 2018-05-21 at 12:04 +0100, George Dunlap wrote:
> On Thu, May 17, 2018 at 4:12 PM, Ian Jackson <ian.jackson@citrix.com>
> 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 work if you will help debug it,
> > review logs, tell me what to do next, etc. :-).
> 
> I'm pretty sure it would be possible to test the Xen "get ready for
> suspend" and "resume from suspend" functionality without actually
> needing to interact with ACPI -- we just get it to the point where it
> would start interacting with ACPI, and then have it return instead.
> From a "I'm positive this will continue to work" point of view it's
> not as satisfying as actually doing the suspend; but from a practical
> point of view, it will catch the vast majority of bugs in Xen (as
> opposed to hardware-specific quirks); and it will run on any hardware
> (which means not having to do reliability testing).
> 
> IIRC Dario actually had a patch for something like this for his own
> testing at some point -- Dario, anything to add?
> 
Indeed I had a patch (it's originally from Ben, actually). I sent it,
so it can be found in list archives. And, in any case, I still have it
around and can resend it.

I did catch quite a few bugs with it back then.

> 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 that works reliably; 3) default all
> hardware to 'false' until we do some testing to find out how reliable
> it is?
> 
> That way we get suspend testing 95% effective as quickly as possible,
> and we can complete it as we have time.
> 
That sounds a very good plan to me, FWIW.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

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

  reply	other threads:[~2018-05-21 11:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16 21:54 Test for osstest, features used in Qubes OS Marek Marczykowski-Górecki
2018-05-17 12:26 ` Ian Jackson
2018-05-17 14:59   ` Marek Marczykowski-Górecki
2018-05-17 15:12     ` Ian Jackson
2018-05-17 18:00       ` Sander Eikelenboom
2018-05-18 15:44         ` Marek Marczykowski-Górecki
2018-05-18 15:33       ` Marek Marczykowski-Górecki
2018-05-18 15:54         ` Jan Beulich
2018-05-18 16:19           ` Marek Marczykowski
2018-05-21 15:48             ` George Dunlap
2018-05-21 16:17               ` Andrew Cooper
2018-05-21 16:28                 ` George Dunlap
2018-05-21 17:18                   ` George Dunlap
2018-05-22 22:21               ` Simon Gaiser
2018-05-24 13:15                 ` Jan Beulich
2018-05-24 13:39                   ` Simon Gaiser
2018-05-21 11:04       ` George Dunlap
2018-05-21 11:52         ` Dario Faggioli [this message]
2018-05-21 13:57           ` Ian Jackson
2018-05-21 14:11             ` George Dunlap
2018-05-22  7:51             ` Dario Faggioli
2018-05-21 11:49       ` Dario Faggioli

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=b713974db1f90fcf450ce232761dab0defb3ee8a.camel@suse.com \
    --to=dfaggioli@suse.com \
    --cc=dunlapg@umich.edu \
    --cc=ian.jackson@citrix.com \
    --cc=marmarek@invisiblethingslab.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).