From: Ayan Kumar Halder <ayankuma@amd.com>
To: Julien Grall <julien.grall.oss@gmail.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@citrix.com>,
"Bertrand Marquis" <Bertrand.Marquis@arm.com>,
"Henry Wang" <Henry.Wang@arm.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"community.manager@xenproject.org"
<community.manager@xenproject.org>,
"jgross@suse.com" <jgross@suse.com>,
"sstabellini@kernel.org" <sstabellini@kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.18 release: Reminder about feature/code freeze
Date: Mon, 11 Sep 2023 09:23:13 +0100 [thread overview]
Message-ID: <23604843-555f-4e34-fd6a-53bbe7f94d68@amd.com> (raw)
In-Reply-To: <CAJ=z9a2LpUe_9160PEChMG=pSLYcwLwETdrTN2zDrk21QP2qpw@mail.gmail.com>
Hi Julien,
On 11/09/2023 09:09, Julien Grall wrote:
>
>
> On Mon, 11 Sep 2023 at 09:02, Ayan Kumar Halder <ayankuma@amd.com> wrote:
>
> Hi Henry,
>
> On 11/09/2023 02:08, Henry Wang wrote:
> > CAUTION: This message has originated from an External Source.
> Please
> > use proper judgment and caution when opening attachments, clicking
> > links, or responding to this email.
> >
> > Hi everyone,
> >
> > This is the reminder that we are currently in the feature freeze. I
> > apologise
> >
> > for the delay.
> >
> > I decided to make the code freeze date on Fri Sep 22, 2023, to give
> > people more
> >
> > time to react because of my late reminder about feature freeze. The
> > hard code
> >
> > freeze date will remain unchanged, i.e. Fri Oct 6, 2023. So
> currently
> > we have 2
> >
> > weeks before code freeze and another 4 weeks before hard code
> freeze. If
> >
> > everything goes well, we can cut 4.18 rc1 at Fri Sep 29, 2023.
> >
> > Also, below is the critical items on my list for 4.18 release:
> >
> > 1. [PATCH 0/7] tools: More Python 3 fixes (part 1 of N)
> >
> > https://gitlab.com/xen-project/xen/-/issues/114
> >
> > 2. tools: Switch to non-truncating XENVER_* ops
> >
> >
> https://lore.kernel.org/xen-devel/20230117135336.11662-1-andrew.cooper3@citrix.com/
> >
> > 3. dom0less vs xenstored setup race Was: xen | Failed pipeline for
> > staging | 6a47ba2f
> >
> > https://marc.info/?l=xen-devel&m=168312468808977
> <https://marc.info/?l=xen-devel&m=168312468808977>
> > <https://marc.info/?l=xen-devel&m=168312468808977
> <https://marc.info/?l=xen-devel&m=168312468808977>>
> >
> > https://marc.info/?l=xen-devel&m=168312687610283
> <https://marc.info/?l=xen-devel&m=168312687610283>
> > <https://marc.info/?l=xen-devel&m=168312687610283
> <https://marc.info/?l=xen-devel&m=168312687610283>>
> >
> > 4. The proper eIBRS support for x86
> >
> >
> https://lore.kernel.org/xen-devel/ec8e75da-743b-50dc-4665-854c446c974e@citrix.com/
> >
> > 5. [PATCH 1/2] credit: Limit load balancing to once per millisecond
> >
> >
> https://lore.kernel.org/xen-devel/20230630113756.672607-1-george.dunlap@cloud.com/
> >
> > 6. [PATCH 0/2] Revoke IOMEM/IO port/IRQ permissions on PCI
> detach for
> > HVM guest
> >
> >
> https://lore.kernel.org/xen-devel/20230809103305.30561-1-julien@xen.org/
> >
> > 7. [PATCH v2 0/8] Fixes to debugging facilities
> >
> >
> https://lore.kernel.org/xen-devel/21cc28b9-91d1-1e6e-23ac-00c44f3ec08e@gmail.com/
> >
>
> Did you miss "[PATCH v6 00/13] xen/arm: Split MMU code as the
> prepration
> of MPU work" ?
>
>
> AFAIU Henry listed all the critical series for 4.18. Can you explain
> why do you think this is one?
Sorry, if I misunderstood something.
I assumed we were aiming for R82 MMU rework to be included in 4.18 release.
- Ayan
>
> Cheers,
>
>
>
> It see that patches from [PATCH v6 06/13] xen/arm: Split page table
> related code to mmu/pt.c ... are yet to be reviewed and committed.
>
> - Ayan
>
> > Kind regards,
> >
> > Henry
> >
>
next prev parent reply other threads:[~2023-09-11 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 1:08 Xen 4.18 release: Reminder about feature/code freeze Henry Wang
2023-09-11 7:10 ` Jan Beulich
2023-09-11 8:01 ` Ayan Kumar Halder
2023-09-11 8:09 ` Julien Grall
2023-09-11 8:22 ` Henry Wang
2023-09-11 8:23 ` Ayan Kumar Halder [this message]
2023-09-11 8:30 ` Julien Grall
2023-09-22 13:50 ` Andrew Cooper
2023-09-22 14:45 ` George Dunlap
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=23604843-555f-4e34-fd6a-53bbe7f94d68@amd.com \
--to=ayankuma@amd.com \
--cc=Bertrand.Marquis@arm.com \
--cc=Henry.Wang@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=community.manager@xenproject.org \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien.grall.oss@gmail.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.