qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: Marcel Apfelbaum <mapfelba@redhat.com>,
	seabios <seabios@seabios.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	David Gilbert <dgilbert@redhat.com>, Bandan Das <bsd@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [SeaBIOS] seabios stable release
Date: Thu, 12 Mar 2015 17:34:11 +0100	[thread overview]
Message-ID: <1426178051.1722.24.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <20150311183140.GA308@morn.localdomain>

On Mi, 2015-03-11 at 14:31 -0400, Kevin O'Connor wrote:
> On Wed, Mar 11, 2015 at 02:48:18PM +0100, Gerd Hoffmann wrote:
> >   Hi,
> > 
> > Looks like we need a stable release branch for 1.8 and roll out a 1.8.1
> > release with some fixes for qemu.
> > 
> > Issue #1: support for multiple pci roots.
> > 
> > Issue #2: There is a (not-yet fixed) emulation failure with newer intel
> > processors, apparently triggered by seabios commit
> > 0673b7870063a3affbad9046fb6d385a4e734c19
> > 
> > Thread starts here:
> >   https://lists.gnu.org/archive/html/qemu-devel/2015-03/msg01140.html
> > 
> > Other known issues in 1.8 which should be addressed in 1.8.1?
> 
> I think the PVSCSI fix (bc82fa43) should go in.

Branch created, three patches (2x pvscsi + 1x multiple pci root)
cherry-picked from master, pushed.

The smp race fix will follow as soon as it hits master.

More candidates?

I plan to tag 1.8.1 tomorrow or next monday, so the release will be
ready in time for qemu 2.3-rc0 which is planned for next tuesday.

cheers,
  Gerd

  reply	other threads:[~2015-03-12 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 13:48 [Qemu-devel] seabios stable release Gerd Hoffmann
2015-03-11 18:31 ` Kevin O'Connor
2015-03-12 16:34   ` Gerd Hoffmann [this message]
2015-03-16  7:56     ` [Qemu-devel] [SeaBIOS] " Gerd Hoffmann

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=1426178051.1722.24.camel@nilsson.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=bsd@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=mapfelba@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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).